Since the instructions appeared to reference steps in the path that doesn't exist when installing from Apps & Marketplace, I updated with a path that is shorter and correct for 2.6.x
We're still seeing lots of OOM events from WAL compaction, and these defaults are not good for all environments. I have attempted to address this in the docs by adding a best practice of tuning resource limits and mentioning the issue in known issues.
In my experience, it can go a long way to clarifying sentences and we use it all over the docs (including many times on this very page) so added it here
Standardized names and etc.
Used `operator: Exists` toleration from the rancher overlay test rather than the no schedule and execute from the RKE.
Added some verbosity
RKE and Rancher had different versions of the test. I synced them and changed them so that they utilize Murali's swiss-army-knife which allows much more freedom for troubleshooting.
I vaguely pulled some of the best practices that I know of and come up often from the docs I cited, but there may be more or more implicit instructions we could provide
Clarified and added a space, moved the result to the end of the instructions to match prior pages and intuitive format, and swapped 'cluster' for 'project' as there is no import yaml option in the cluster view. This last one could do with some investigation as I'm not sure if it was maybe saying to go to the project, import the yaml, and choose the Cluster 'Import Mode' (Options are Cluster, Project, and Namespace). I'm not sure which should be chosen and it might be worth clarifying on all YAML import steps.
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.
Better to be explicit than implicit. There was some confusion on what this was referring to since the section was written with an implicit context that the customer and I were lacking. I've attempted to add the context here.
Tejeevandmartyav
