Veritas InfoScale™ for Kubernetes Environments 8.0.200 - 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
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Veritas InfoScale on Kubernetes
- Introduction
- Prerequisites
- Installing the Special Resource Operator
- Tagging the InfoScale images on Kubernetes
- Applying licenses
- Tech Preview: Installing InfoScale on an Azure Kubernetes Service(AKS) cluster
- Considerations for configuring cluster or adding nodes to an existing cluster
- Installing InfoScale on Kubernetes
- Installing InfoScale by using the plugin
- Undeploying and uninstalling InfoScale
- 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
- 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
Additional prerequisites to install by using yaml
Complete the following steps on the bastion node
- Copy the following images to the local registry.
${LOCAL_REGISTRY}/veritas OS_VER=<OS Version> # eg: 'rhel8.4' KERNEL=<Kernel Version of worker>'# eg: 4.18.0-305.45.1.el8_4.x86_64'cert-manager Images
quay.io/jetstack/cert-manager-cainjector:v1.7.1
quay.io/jetstack/cert-manager-controller:v1.7.1
quay.io/jetstack/cert-manager-webhook:v1.7.1
SRO Images
registry.redhat.io/openshift4/ose-kube-rbac-proxy
registry.redhat.io/openshift4/special-resource-rhel8-operator:<vTAG> where, vTAG=v4.10.0-202206171549.p0.g034862e.assembly.stream or v4.9.0
Operator Image
registry.connect.redhat.com/veritas-technologies/infoscale-sds-operator:8.0.200-rhel8
registry.connect.redhat.com/veritas-technologies/infoscale-licensing-operator:8.0.200-rhel8
To copy images to ${LOCAL_REGISTRY}
If mirror host is connected to internet and
${LOCAL_REGISTRY}both, run the following commands on mirror hostpodman pull <src image> podman tag <src image> <tgt image> podman push <tgt image> #If csi images push fail, try push with '--remove-signatures'
If mirror host is connected to internet only, run the following commands on the mirror host
podman pull <src image> podman save -o <image_name>.tar <src image> <tgt image> -> Copy tar to ${LOCAL_REGISTRY} connected host (bastion node)Run the following commands on the bastion node.
podman load -i <image_name>.tar podman tag <src image> <tgt image> podman push <tgt image>
- Update YAML
Update
YAML/OpenShift/air-gapped/*.yamlwith your${LOCAL_REGISTRY}. Run the following commands.cd YAML/OpenShift/air-gapped-systems sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" cert-manager.yaml sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" iso.yaml sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" lico.yaml sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" cr.yaml
Note:
Ensure that you change the image path in all yamls to the local registry address.