* #536 Updating info about nginx helm charts
* versioned docs + eks
* rm'd link to wrong compatibility table
* reworded instructions and added command to see helm chart app versions
* updated commands
* one more
* spacing
* Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
* updated version numbers
* Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
---------
Co-authored-by: Billy Tat <btat@suse.com>
* #501 Undocumented feature flags in 2.7.x
did a refresh of the feature flag page while waiting for a response to request for blurbs
* undocumented features listed with blurbs based on the UI
* typo fix
* Apply suggestions from code review
Co-authored-by: Brad Davidson <brad@oatmail.org>
* note about discontinued flags, rewording descriptions, updated table to rm things that have been available since before 2.5
* added rke1 flag info, updated 2.6 page
* added 2.5 page
* rm'd pointless column from 2.5 table
* updated based on suggestions from code review
* rm'd specific mention of version
* Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
---------
Co-authored-by: Brad Davidson <brad@oatmail.org>
Co-authored-by: Billy Tat <btat@suse.com>
* Addressing request to re-add notes regarding 2.6
* versioned docs updated as well
* rm'ed note from page that didn't need it added back
* zh pages + missing en page
* #77 Addressing backlog issue about imported registered RKE2 clusters
* Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
---------
Co-authored-by: Billy Tat <btat@suse.com>
A new to k3s user might get "surprised" by error messages from kubectl
or k3s like:
WARN[0000] Unable to read /etc/rancher/k3s/k3s.yaml, please start server with --write-kubeconfig-mode to modify kube config permissions
error: error loading config file "/etc/rancher/k3s/k3s.yaml": open /etc/rancher/k3s/k3s.yaml: permission denied
It can happen when there is a k3s installed on the same machine and
`/etc/rancher/k3s/k3s.yaml` present.
Signed-off-by: Kyr Shatskyy <kyrylo.shatskyy@suse.com>
Instead of sending user to find the real number k3s tag format,
just give recent version of k3s which is needed by latest
rancher.
It would be great to update this value automatically, but I have
no good idea how to do this at the moment.
Signed-off-by: Kyr Shatskyy <kyrylo.shatskyy@suse.com>
Move the clause about INSTALL_K3S_VERSION before get.k3s.io
cluster installation command example to emphasize its requirement
to get the correct version of k3s on which the rancher should will
be installed, because it can be an annoying mistake that user might
start from setup from scratch.
Signed-off-by: Kyr Shatskyy <kyrylo.shatskyy@suse.com>
