You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in #33, Security Context Constraints (AKA SCCs) should be fined tuned for each of the PODs when deploying attestation operator in OpenShift.
Why? the reason for that boils down to regulations/compliance in a lot of companies that prohibit the use of already existing SCCs (such as anyuid, which is the one being used currently for OpenShift deployment). However, companies are fine if there are dedicated SCCs for the specific use-cases that also must not be used for anything else.
The text was updated successfully, but these errors were encountered:
As discussed in #33, Security Context Constraints (AKA SCCs) should be fined tuned for each of the PODs when deploying attestation operator in OpenShift.
Why? the reason for that boils down to regulations/compliance in a lot of companies that prohibit the use of already existing SCCs (such as anyuid, which is the one being used currently for OpenShift deployment). However, companies are fine if there are dedicated SCCs for the specific use-cases that also must not be used for anything else.
The text was updated successfully, but these errors were encountered: