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.

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

[Documentation] Explain node pre-reqs #857

Closed
davidnuzik opened this issue Oct 2, 2019 · 2 comments · Fixed by rancher/docs#1958
Closed

[Documentation] Explain node pre-reqs #857

davidnuzik opened this issue Oct 2, 2019 · 2 comments · Fixed by rancher/docs#1958
Assignees
Labels
kind/documentation Improvements or additions to documentation
Milestone

Comments

@davidnuzik
Copy link
Contributor

davidnuzik commented Oct 2, 2019

We need to ensure that our documentation clearly states any/all pre-requisites for a node (VM).

For example:

Provide any FYIs / Gotchas

  • if create master node with --disable-agent flag no node is shown when get nodes because kubelet does not run, this is expected.
  • if create worker node (in what scenario?) it will not show as master node when get nodes.
@davidnuzik
Copy link
Contributor Author

Any pre-reqs such as iptables, and other requirements mentioned in #982 should also be taken into consideration.

@davidnuzik
Copy link
Contributor Author

davidnuzik commented Oct 31, 2019

  • --disable-agent is no longer advertised (flag is still there and usable but hidden in docs and cli. It is not recommended. As such i won't include this.
  • SWAP is generally a known thing. K8s states this in official documentation around the kubelet. It could be a candidate for FAQ at some point if enough people complain about it but it doens't belong on the node pre-reqs page in the docs.
  • iptables issue is something for the new "Known Issues" section and will be handled separately here: [Documentation] FAQ and Known Issues sections #984

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant