* #462 Add Add instructions for how to use PSACT
* started adding instructions for adding/editing a cluster
* started adding instructions for add/editing a psa template
* instructions for rke2/k3s, note about cis
* updated to include RKE1 instructions
* wording
* nipicky word choice: applied > described
* Apply suggestions from code review
Co-authored-by: Jiaqi Luo <6218999+jiaqiluo@users.noreply.github.com>
* tabs, added suggestion on RKe2 link from thread
* sidebars, correcting language in hardening guide
* link, switching where list of exempt namespaces is placed, corrections - users edit the PSA config, not PSS, to establish restrictions on pods
* update link
* added final save/create instructions
* Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
* updated file names
* missing metadata key
* corrected links
* Delete psa-config-template.md
File shouldn't still be in the tree, as it was renamed
* Apply suggestions from code review
Co-authored-by: Jiaqi Luo <6218999+jiaqiluo@users.noreply.github.com>
* syncing RKE1 and 2 hardening guides, title update
* moved sample config file, added - to list of required exempt namespaces
* added moved config file to sidebars.js
---------
Co-authored-by: Jiaqi Luo <6218999+jiaqiluo@users.noreply.github.com>
Co-authored-by: Billy Tat <btat@suse.com>
* #300 Missing documentation: Rancher monitoring requires port 10254
* capitalization
* line break typo
* typo in heading
* additional context for when you may have to open port 10254
* reworded note about 10254 and v1/pushprox
* clarified what setting indicates pushprox is disabled
* typo
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>
