Please enter search query.
Search <book_title>...
Veritas InfoScale™ for Kubernetes Environments 8.0.220 - Linux
Last Published:
2023-10-16
Product(s):
InfoScale & Storage Foundation (8.0.220)
Platform: Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Veritas InfoScale on Kubernetes
- Prerequisites
- Tagging the InfoScale images on Kubernetes
- Installing InfoScale on Kubernetes
- Configuring KMS-based Encryption on an OpenShift cluster
- Configuring KMS-based Encryption on a Kubernetes cluster
- InfoScale CSI deployment in Container environment
- Dynamic provisioning
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Installing and configuring InfoScale DR Manager on OpenShift
- Installing and configuring InfoScale DR Manager on Kubernetes
- Disaster Recovery scenarios
- Configuring InfoScale
- Administering InfoScale on Containers
- Upgrading InfoScale
- Troubleshooting
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"