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
This PR exposes a spec.runAsRoot field, so that cluster admins can
indicate that they want to run the catalogsource container as root
user.
This, along with the Pod Admission Controller enforce level `privileged`
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]>
Copy file name to clipboardExpand all lines: deploy/chart/crds/0000_50_olm_00-catalogsources.crd.yaml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -79,6 +79,9 @@ 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 so that the pod can be run in PSA `privileged` namespace. By default, SecurityContextConfig is set to `restricted`. If a value other than `legacy` or `restricted` is used as input, the default value is set instead of using the incorrect value When using older catalog images, which could not be run in restricted mode, the SecurityContextConfig should be set to `legacy`. More info about PSA can be found here: https://kubernetes.io/docs/concepts/security/pod-security-admission/'
84
+
type: string
82
85
tolerations:
83
86
description: Tolerations are the catalog source's pod's tolerations.
84
87
type: array
@@ -120,9 +123,6 @@ spec:
120
123
type: integer
121
124
publisher:
122
125
type: string
123
-
runAsRoot:
124
-
description: RunAsRoot allows admins to indicate that they wish to run the CatalogSource pod in a privileged pod as root. This should only be enabled when running older catalog images which could not be run as non-root.
125
-
type: boolean
126
126
secrets:
127
127
description: Secrets represent set of secrets that can be used to access the contents of the catalog. It is best to keep this list small, since each will need to be tried for every catalog entry.
0 commit comments