RKE2 Cluster - Need Assistance with Privileged Pods in Kubernetes v1.26.10+rke2r2

[AichaDevOps]

Hello Community,

I am currently encountering challenges with my RKE2 Kubernetes cluster, running version v1.26.10+rke2r2. The default admission control mode in my cluster is set to privileged, which is proving to be too restrictive for my applications.

I have attempted to adjust the admission control mode at the namespace level to baseline to provide less restriction. However, despite this adjustment, I am still facing issues running pods that require the privileged setting to be true.

Here are the key details:

Kubernetes Version: v1.26.10+rke2r2
Admission Control Mode: Default is privileged, adjusted at the namespace level to baseline.
Issue: Unable to run pods requiring privileged setting even after adjusting the admission control mode to baseline at the namespace level.
I have reviewed the RKE2 documentation, but the information on handling admission control modes in a more granular way, especially for specific pods or containers within a namespace, is not clear.

Could someone kindly provide guidance on how to fine-tune admission control modes for specific pods or containers in RKE2, especially in version v1.26.10+rke2r2? I need to ensure that pods with specific privilege requirements can run successfully within the cluster.

Any assistance, insights, or relevant documentation pointers would be greatly appreciated.

Thank you for your time and support.

Best regards,