-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
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
[BUG] RKE2 hardened cluster fails to provision for k8s 1.25.5 #39148
Comments
/backport v2.6.9 |
@rishabhmsra , my understanding is that
If that's correct, let's close this bug, as well as the backport. |
Now that 2.7-head runs k8s 1.25, there are no profiles that can run on a RKE2 hardened cluster. #39851 (comment) shows that CIS can run on other cluster types, even with the 1.23 profile. I am increasing the priority of this ticket to priority/0 until QA or product approves the behavior. |
@rishabhmsra , I talked to Sergey. Can you add/update the exact reproduction steps for the current 2.7head? thanks. |
Hey @MKlimuszka @snasovich, The steps to reproduce this on 2.7 head are mentioned in the issue description. The behaviour which I saw on k8s 1.25 with cis-profile 1.6 was that it was stuck in updating state with the msg as follows:
And while using the 1.23 profile it was stuck at:
|
@doflamingo721 , per https://docs.rke2.io/security/hardening_guide The way I'm reading your previous comment it looks like RKE2 provisioning on k8s 1.25.5 seems to fail when |
@snasovich I have updated the issue description with the steps to reproduce the behaviour and the relevant logs. |
When
Making |
@rishabhmsra please validate the same issue when this issue is fixed - #39994 |
Is this for CIS scans or the CIS profile that's launched when RKE2 starts? There is a difference between the two that people have been confusing. |
@deniseschannon , CIS profile. |
Moving this issue to test as #39994 is ready to test |
Tested the issue on rancher v2.7-head. Hardened k8s cluster version v1.25.6+rke2r1 provisioned successfully with CIS profile 1.23. Test steps.
Node registration is successful. Hardened k8s cluster v1.25.6+rke2r1 provisioning was successful with CIS profile 1.23. Hence, closing the issue. |
Rancher Server Setup
Information about the Cluster
User Information
Describe the bug
To Reproduce
For cis profile 1.23 ->
Followed the hardening steps from here #36629 (comment)
/etc/sysctl.d/90-kubelet.conf
configured:sudo sysctl -p /etc/sysctl.d/90-kubelet.conf
to enable the settingssudo useradd -r -c "etcd user" -s /sbin/nologin -M etcd -U
Set profile to cis-1.23
Result
Provisioning logs:
Below are the logs on etcd node:
rancher-system-agent:
rke2-server.service
Expected Result
The text was updated successfully, but these errors were encountered: