Veritas InfoScale™ for Kubernetes Environments 8.0.300 - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Introduction
- Prerequisites
- Additional Prerequisites for Azure RedHat OpenShift (ARO)
- Considerations for configuring cluster or adding nodes to an existing cluster
- Creating multiple InfoScale clusters
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Removing and adding back nodes to an Azure RedHat OpenShift (ARO) cluster
- Installing Veritas 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
- CSI plugin deployment
- Raw block volume support
- Static provisioning
- Dynamic provisioning
- Resizing Persistent Volumes (CSI volume expansion)
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Using InfoScale with non-root containers
- Using InfoScale in SELinux environments
- CSI Drivers
- Creating CSI Objects for OpenShift
- Creating ephemeral volumes
- 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
- Migrating applications to 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.
Following are the FileSystem-persistent volumes features which are supported on Block volumes.
Create and Delete Volumes
Expand Volumes
Clone Volumes
Create and Delete Snapshot
Snapshot Restore
Note:
Access mode RWO (ReadWriteOnce) is not supported for block volumes. Creation of a RWO block volume does not fail. The volume is created with RWX (ReadWriteMany) properties even when it is listed as RWO. For ROX (ReadOnlyMany) block volumes, the read-only condition is enforced on non-root users only.
For Block volumes, the CSI driver does not format the block device; it just binds the block device to the target path.