Veritas InfoScale™ for Kubernetes Environments 8.0.220 - 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
Raw block volume support
Using raw block volume, the block device is directly exposed instead of exposing the mountpoint inside an application container. Applications can directly write or can create their own native filesystem on the provided block device.
Raw block volumes support is required for applications that are capable of accessing the device directly to store data. Database application is an example where data is directly accessed from the underlying storage, which is more efficient. To enable raw block volume support, volumeMode
must be set to Block
. All features supported on FileSystem-persistent volumes are supported on Block volumes. For example:
Create and Delete Volumes
Expand Volumes
Clone Volumes
Create and Delete Snapshot
Snapshot Restore
For Block volumes, the CSI driver does not format the block device; it just binds the block device to the target path.