up.sh labels the inbuxa namespace with pod-security.kubernetes.io/enforce=restricted and warn=restricted, so the lab refuses any chart pod that doesn't pass. This covers the enforcement half of K-L3. Its policy checks are still to do.
The running lab is already labelled, and inbuxa-charts K-C4 was tested under it: every Deployment restarted, the upgrade Job ran, and the sign-in and mail tests pass.
`up.sh` labels the `inbuxa` namespace with `pod-security.kubernetes.io/enforce=restricted` and `warn=restricted`, so the lab refuses any chart pod that doesn't pass. This covers the enforcement half of K-L3. Its policy checks are still to do.
The running lab is already labelled, and inbuxa-charts K-C4 was tested under it: every Deployment restarted, the upgrade Job ran, and the sign-in and mail tests pass.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
up.shlabels theinbuxanamespace withpod-security.kubernetes.io/enforce=restrictedandwarn=restricted, so the lab refuses any chart pod that doesn't pass. This covers the enforcement half of K-L3. Its policy checks are still to do.The running lab is already labelled, and inbuxa-charts K-C4 was tested under it: every Deployment restarted, the upgrade Job ran, and the sign-in and mail tests pass.