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
(psa) allow legacy Catalogsources to run in non-restrcted namespaces (#2845)
* (chore) vendor in o-f/api v0.17.1
Signed-off-by: Anik Bhattacharjee <[email protected]>
* (psa) allow legacy Catalogsources to run in non-restrcted namespaces
This PR configures the Catalogsource reconciler to use the spec.GrpcPodConfig.SecurityContextConfig
field to determine if the pod.spec.securityContext and container[*].spec.SecurityContext for the registry
pod should be configured to be runnable in a PSA restrcited namespace or not, so that cluster admins can
indicate that they want to run legacy catalogsources in a non-resctricted (baseline/privileged) namespace.
This allows cluster admins to run catalogsources that are built with a version of opm that is less than
v1.23.2 (i.e a version of opm that does not contain [this commit](operator-framework/operator-registry#974)
Signed-off-by: Anik Bhattacharjee <[email protected]>
Signed-off-by: Anik Bhattacharjee <[email protected]>
Copy file name to clipboardExpand all lines: deploy/chart/crds/0000_50_olm_00-catalogsources.crd.yaml
+7
Original file line number
Diff line number
Diff line change
@@ -79,6 +79,13 @@ spec:
79
79
priorityClassName:
80
80
description: If specified, indicates the pod's priority. If not specified, the pod priority will be default or zero if there is no default.
81
81
type: string
82
+
securityContextConfig:
83
+
description: 'SecurityContextConfig can be one of `legacy` or `restricted`. The CatalogSource''s pod is either injected with the right pod.spec.securityContext and pod.spec.container[*].securityContext values to allow the pod to run in Pod Security Admission(PSA) controller''s `restricted` mode, or doesn''t set these values at all, in which case the pod can only be run in PSA `baseline` or `privileged` namespaces. By default, SecurityContextConfig is set to `restricted`. If the value is unspecified, the default value of `restricted` is used. Specifying any other value will result in a validation error. When using older catalog images, which could not be run in `restricted` mode, the SecurityContextConfig should be set to `legacy`. More information about PSA can be found here: https://kubernetes.io/docs/concepts/security/pod-security-admission/'''
84
+
type: string
85
+
default: restricted
86
+
enum:
87
+
- legacy
88
+
- restricted
82
89
tolerations:
83
90
description: Tolerations are the catalog source's pod's tolerations.
0 commit comments