12.3. Example security context constraints

allowHostDirVolumePlugin: true
allowHostIPC: true
allowHostNetwork: true
allowHostPID: true
allowHostPorts: true
allowPrivilegedContainer: true
allowedCapabilities: 

- '*'
apiVersion: security.openshift.io/v1
defaultAddCapabilities: [] 

fsGroup: 

  type: RunAsAny
groups: 

- system:cluster-admins
- system:nodes
kind: SecurityContextConstraints
metadata:
  annotations:
    kubernetes.io/description: 'privileged allows access to all privileged and host
      features and the ability to run as any user, any group, any fsGroup, and with
      any SELinux context.  WARNING: this is the most relaxed SCC and should be used
      only for cluster administration. Grant with caution.'
  creationTimestamp: null
  name: privileged
priority: null
readOnlyRootFilesystem: false
requiredDropCapabilities: [] 

runAsUser: 

  type: RunAsAny
seLinuxContext: 

  type: RunAsAny
seccompProfiles:
- '*'
supplementalGroups: 

  type: RunAsAny
users: 

- system:serviceaccount:default:registry
- system:serviceaccount:default:router
- system:serviceaccount:openshift-infra:build-controller
volumes:
- '*'

apiVersion: v1
kind: Pod
metadata:
  name: security-context-demo
spec:
  securityContext: 

  containers:
  - name: sec-ctx-demo
    image: gcr.io/google-samples/node-hello:1.0

apiVersion: v1
kind: Pod
metadata:
  name: security-context-demo
spec:
  securityContext:
    runAsUser: 1000 

  containers:
    - name: sec-ctx-demo
      image: gcr.io/google-samples/node-hello:1.0