WIP: Openshift 4.11 Pod security standards #260
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| kind: ClusterRole | ||
| apiVersion: rbac.authorization.k8s.io/v1 | ||
| metadata: | ||
| name: pipelines-scc-clusterrole | ||
| rules: | ||
| - verbs: | ||
| - use | ||
| apiGroups: | ||
| - security.openshift.io | ||
| resources: | ||
| - securitycontextconstraints | ||
| resourceNames: | ||
| - pipelines-scc-v2 | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| --- | ||
| allowHostPorts: false | ||
| priority: 10 | ||
| requiredDropCapabilities: | ||
| - MKNOD | ||
| allowPrivilegedContainer: false | ||
| runAsUser: | ||
| type: RunAsAny | ||
| users: [] | ||
| allowHostDirVolumePlugin: false | ||
| allowHostIPC: false | ||
| seLinuxContext: | ||
| type: MustRunAs | ||
| readOnlyRootFilesystem: false | ||
| metadata: | ||
| annotations: | ||
| include.release.openshift.io/ibm-cloud-managed: 'true' | ||
| include.release.openshift.io/self-managed-high-availability: 'true' | ||
| include.release.openshift.io/single-node-developer: 'true' | ||
|
Comment on lines
+17
to
+19
There was a problem hiding this comment. We don't need these - these are special annotations used by OLM for OpenShift (I believe) |
||
| kubernetes.io/description: >- | ||
| pipelines-scc-v2 is a close replica of pipelines-scc scc. pipelines-scc-v2 has allowPrivilegeEscalation=false. | ||
| release.openshift.io/create-only: 'true' | ||
|
There was a problem hiding this comment. Likewise - I don' think we need this, since ArgoCD is going to be doing the syncing. |
||
| generation: 1 | ||
| name: pipelines-scc-v2 | ||
| fsGroup: | ||
| type: MustRunAs | ||
| groups: | ||
| - 'system:cluster-admins' | ||
| kind: SecurityContextConstraints | ||
| defaultAddCapabilities: null | ||
| supplementalGroups: | ||
| type: RunAsAny | ||
| volumes: | ||
| - configMap | ||
| - downwardAPI | ||
| - emptyDir | ||
| - persistentVolumeClaim | ||
| - projected | ||
| - secret | ||
| allowHostPID: false | ||
| allowHostNetwork: false | ||
| allowPrivilegeEscalation: false | ||
| apiVersion: security.openshift.io/v1 | ||
| allowedCapabilities: | ||
| - SETFCAP | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the key question is if this ClusterRole needs to be created on the workload cluster, or if it needs to be created in KCP.