Please enter search query.
Search <book_title>...
Veritas InfoScale™ for Kubernetes Environments 8.0.300 - Linux
Last Published:
2023-12-12
Product(s):
InfoScale & Storage Foundation (8.0.300)
- 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
Creating multiple InfoScale clusters
After successfully installing InfoScale operator, you can create a cluster.
You can configure multiple clusters in different namespaces. After a cluster is configured and pods are created successfully, you can update cr.yaml with the name, namespace, Cluster ID, and node-related information of the next cluster. You can choose to rename cr.yaml or you can overwrite the same cr.yaml. You can then create the cluster and after a successful creation of pods, update cr.yaml for the subsequent cluster. Likewise, you can configure multiple clusters.
Each InfoScale cluster must have a unique name even when clusters are created across namespaces.