security: add annotation for validated SCC type #2211
Conversation
|
Hello @ibihim! Some important instructions when contributing to openshift/api: |
openshift-ci
bot
added
the
size/XS
|
/lgtm |
An SCC is being assigned to a workload based on the capabilities the ServiceAccount or user has. To distinct, against whom this was validated against, this annotation is being introduced.
ibihim
force-pushed
the
ibihim/2025-02-25_validated-scc-type-annotation
branch
from
45b49aa to
09148e8
Compare
|
Do we have enough consensus on the enhancement to feel confident in adding this? What would you do if the EP pivots away from using this? |
|
@JoelSpeed, we need this anyway. Without that annotation, we can't close a major gap in our violation scan that happens within CFE. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ibihim, JoelSpeed, kramaranya The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@ibihim: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] Distgit: ose-cluster-config-api |
What
Add annotation for validated SCC type (User / ServiceAccount).
Why
An SCC is being assigned to a workload based on the capabilities the ServiceAccount or user has. To distinct, against whom this was validated against, this annotation is being introduced.
This is necessary to identify namespaces that might not be labeled properly by the PSA label syncer as it doesn't watch the user's SCCs and picks the wrong PodSecurityStandard for PodSecurityAdmission labels.
Reference