Using InfoScale with non-root containers
While using InfoScale with containers that are not running as the root user, the storage ownership might need to be changed to ensure that the containers are able to read or write to the file system. You can specify an
fsGroup attribute in the pod security context to enable read or write. Using the fsGroup attribute instructs OpenShift or Kubernetes to change the ownership of the file system to the specified group. It also instructs runtime to add the specified group to the supplemental groups the container is run with. This ensures that the container processes are able to read and write files in the volume. In the following example securityContext includes an explicit fsGroup
securityContext:
runAsUser: 1000
runAsGroup: 3000
fsGroup: 5000
fsGroupChangePolicy: "OnRootMismatch"
Related information