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
Prerequisites to install by using YAML or OLM
A few operators are needed to install InfoScale by using OLM. As air gapped/restricted networks are disconnected from the internet, operators must be mirrored to local registry. For mirroring, it requires a host having internet as well as local registry connection, named mirror-host.
Complete the following steps on the mirror-host
where ${LOCAL_REGISTRY}
is accessible. For others, see https://docs.openshift.com/container-platform/4.11/installing/disconnected_install/installing-mirroring-disconnected.html
Note:
In the following steps, ${LOCAL_REGISTRY} is on the same network. LOCAL_REGISTRY is a system connected to the mirror-host but disconnected from Internet,and has a registry setup.
- Run the following command to set variables.
export LOCAL_REGISTRY=<local_registry_host_name>:<local_registry_host_port>
- Run the following commands to download and extract the latest
oc-mirror
plugin on the mirror host.wget -4 https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/latest/oc-mirror.tar.gz
tar -xvf oc-mirror.tar.gz -C /usr/local/bin/
chmod 750 /usr/local/bin/oc-mirror
- Download
YAML_8.0.220.tar.gz
from the Veritas Download Centre. - Extract
YAML_8.0.220.tar.gz
. A folderYAML/OpenShift/air-gapped
is created and all files required for installation are available in the folder. - Run the following commands to login to registries.
podman login registry.redhat.io
podman login registry.connect.redhat.com
podman login ${LOCAL_REGISTRY}
- Run oc mirror list operators --catalog <CATALOG> --package <OPERATOR> to update
operators.packages.channels.name
inYAML/OpenShift/air-gapped-systems/imageset-config.yaml
. - Edit
imageset-config.yaml
toReplace
${LOCAL_REGISTRY}
with<local_registry_host_name>:<local_registry_host_port>
.Replace
${OCP_RELEASE}
with theOCP version
.Replace
${OSVER}
withOperating system version of the worker node
.Replace
${KERNVER}
withKernel version of the worker node
.
- Run the following commands on the mirror host to mirror operators.
cd YAML/OpenShift/air-gapped-systems
oc mirror --config=./imageset-config.yaml docker://${LOCAL_REGISTRY}/operators --continue-on-error
Review output as under.
Rendering catalog image "registry.lab.ocp.lan:5000 /operators1/redhat/certified-operator-index:v4.10" with file-based catalog Rendering catalog image "registry.lab.ocp.lan:5000 /operators1/redhat/redhat-operator-index:v4.10" with file-based catalog Writing image mapping to oc-mirror-workspace/results-1669176953/mapping.txt Writing CatalogSource manifests to oc-mirror-workspace/results-1669176953 Writing ICSP manifests to oc-mirror-workspace/results-1669176953
Note:
Here,
registry.lab.ocp.lan
is the local registry and 5000 is an indicative port number. - Optionally, Update
oc-mirror-workspace/results-1669176953/catalogSource-redhat-operator-index.yaml
and- oc-mirror-workspace/results-1669176953/catalogSource-certified-operator-index.yaml
. - Run the following command to copy
oc-mirror-workspace
to the bastion node.scp -r oc-mirror-workspace ocp-svc:~/
- Run the following command on the bastion node to set
disableAllDefaultSources: true
. This disables all sources for the default catalogs.oc patch OperatorHub cluster --type json -p '[{"op": "add", "path": "/spec/disableAllDefaultSources", "value": true}]'
- Run the following commands on the bastion node to deploy the image content source policy and catalog source.
oc create -f oc-mirror-workspace/results-1669176953/imageContentSourcePolicy.yaml
oc create -f oc-mirror-workspace/results-1669176953/catalogSource-redhat-operator-index.yaml
oc create -f oc-mirror-workspace/results-1669176953/catalogSource-certified-operator-index.yaml
- Run the following commands on the bastion node to verify whether the resources are created successfully.
oc get catalogsource -n openshift-marketplace
oc get pods -n openshift-marketplace
oc get packagemanifest -n openshift-marketplace
- Login to the OpenShift web console and check whether the mirrored operators are displayed in Operators > OperatorHub as under
- On the mirror host, Download, unzip, and untar
tools_8.0.220.tar.gz
from theVeritas Download Center. After you unzip and untar,tools/setup_vtas_registry.sh
is automatically created. - Run the following commands on the mirror host.
cd tools
OS_VER=<OS Version> # eg: 'rhel8.4'
KERNEL=<Kernel Version of worker>' # eg: 4.18.0-305.45.1.el8_4.x86_64'
./setup_vtas_registry.sh --airgap -o $OS_VER -k $KERNEL
A folder
infoscale_operand_images.tar
is automatically created. - Copy
infoscale_operand_images.tar
from the mirror host to the bastion node. - Run the following commands to load infoscale images onto local registry from bastion node
OS_VER=<OS Version> # eg: 'rhel8.4'
KERNEL=<Kernel Version of worker>' # eg: 4.18.0-305.45.1.el8_4.x86_64'
podman login ${LOCAL_REGISTRY}
./setup_vtas_registry.sh --airgap -o $OS_VER -k $KERNEL \ -c ${LOCAL_REGISTRY}/veritas -t infoscale_operand_images.tar