Seems small, but can be misleading. There are plenty of options in AWS for configuring permission, etc. But in RKE, there is only one option and that is setting the name of the cloud provider.
* Add custom network plugins info to Rancher docs
* Change 'configmap' to 'add-on manifest'
* Add custom network plugins info to Rancher docs
* Change 'configmap' to 'add-on manifest'
* Edit network plugins section of RKE docs
* Add detailed RKE config example to RKE docs
* Minor edit to custom network plugin section
If you are working through the docs in order it makes sense that the addons are in the cluster.yml but this is not evident if you land on the page from a search.
If you are working through the docs in order it makes sense that the addons are in the cluster.yml but this is not evident if you land on the page from a search.
If you are working through the docs in order it makes sense that the addons are in the cluster.yml but this is not evident if you land on the page from a search.
Explicit > Implicit
The page felt very disjointed and as with the others, if you landed on the page from a search it wasn't clear how to add add-ons so I attempted to clarify this and improve the flow of the page.
Turned the portion that read like un-bulleted bullet points into bullet points, but this is still lacking an explanation on best practice for removing an addon and those bullets could use some elucidation.
- Add children to "Installation Options" covering Node Requirements, Single Server Install, and HA install (Experimental)
- Make some small tweaks as needed to hide "--disable-agent" as per https://github.com/rancher/k3s/issues/891
- Make some miscellaneous tweaks such as to hide "--storage-backend" as this is no longer used and other changes as recommended in a recent internal meeting
claycooper
Catherine Luse
David Nuzik
Denise
Adrian Goins
David Noland
Eamon Bauman
William Jimenez
Catherine Luse
Sebastiaan van Steenis
Alex Seymour
Tejeev
kinarashah
Doctori
Erik Wilson
David Zisky
David Nuzik
Nelson Roberts