Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Documentation website #31

Open
fntlnz opened this issue Jan 14, 2019 · 1 comment · May be fixed by #145
Open

Documentation website #31

fntlnz opened this issue Jan 14, 2019 · 1 comment · May be fixed by #145
Milestone
First release

Comments

@fntlnz
Copy link
Member

fntlnz commented Jan 14, 2019 •
edited

Kubectl trace is becoming quite complex, it has a lot of possible options and commands combinations, also there are features that are not completely clear, like is the namespace parameter used to allocate the kubectl-trace container or it is used to filter the pod, so I think we need to have a documentation website.

The possible options I was considering are:

  • GitHub pages
  • Netlify
@fntlnz fntlnz added this to the First release milestone Jan 14, 2019
@adelbertc
Copy link
Contributor

@fntlnz I can try working on this a bit on the weekends. I'm thinking Hugo (Jekyll gives me shivers) + GitHub pages for simplicity to start?

@adelbertc adelbertc linked a pull request Nov 14, 2020 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
First release
Development

Successfully merging a pull request may close this issue.

feat: Move README docs to GitHub pages adelbertc/kubectl-trace
2 participants
@adelbertc @fntlnz