* Reorganize node requirements
* Cherry pick 'Fix links' commit
* Cherry pick 'Link to RKE port requirements for each node in Rancher docs'
* Fix merge conflict errors
* Delete page that was moved elsewhere
* Delete section that was included elsewhere
* Re-add port requirements for custom nodes
* Rearrange pages
* Change wording of note in Rancher installation requirements
* Fix links
* Edit links
* Edit links
* Replace user cluster requirements page
* Fix typo
* Fix link to imported cluster requirements
* Revise node requirements
* Add mini TOC for port requirements
* Remove alias for port requirements page
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.