We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The profile flag is being ignored due to changes made for #2103, which prevents running rke2 in CIS mode with this flag.
Logs from a node:
$ journalctl -eu rke2-server -f -- Logs begin at Wed 2021-12-01 05:24:55 UTC. -- Dec 01 05:28:47 ip-172-31-8-156.us-east-2.compute.internal systemd[1]: Starting Rancher Kubernetes Engine v2 (server)... Dec 01 05:28:47 ip-172-31-8-156.us-east-2.compute.internal systemd[1]: Started Rancher Kubernetes Engine v2 (server). Dec 01 05:28:47 ip-172-31-8-156.us-east-2.compute.internal rke2[14094]: time="2021-12-01T05:28:47Z" level=warning msg="Unknown flag --profile found in config.yaml, skipping\n" Dec 01 05:28:47 ip-172-31-8-156.us-east-2.compute.internal rke2[14094]: time="2021-12-01T05:28:47Z" level=warning msg="not running in CIS mode" ...
Example of problems this causes: https://docs.rke2.io/security/cis_self_assessment15/#1112
$ sudo stat -c %U:%G /var/lib/rancher/rke2/server/db/etcd root:root
The text was updated successfully, but these errors were encountered:
Validated using v1.22.4-rc2+rke2r1 this has been resolved
Sorry, something went wrong.
dereknola
rancher-max
No branches or pull requests
The profile flag is being ignored due to changes made for #2103, which prevents running rke2 in CIS mode with this flag.
Logs from a node:
Example of problems this causes:
https://docs.rke2.io/security/cis_self_assessment15/#1112
The text was updated successfully, but these errors were encountered: