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
Downloading side car images
Following table lists the side car images for CSI plugin and fencing containers. You must download the CSI plugin-related images from https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/asia/sig-storage and the fencing-related images from https://hub.docker.com/r/kvaps/kube-fencing-agents
Note:
Perform these steps if you are manually tagging images instead of using setup_vtas_registry.sh
for tagging images.
Table: Image names and sources for side car containers
Image name | Source |
---|---|
csi-snapshotter | k8s.gcr.io/sig-storage/csi-snapshotter |
csi-provisioner | k8s.gcr.io/sig-storage/csi-provisioner |
csi-resizer | k8s.gcr.io/sig-storage/csi-resizer |
csi-node-driver-registrar | k8s.gcr.io/sig-storage/csi-node-driver-registrar |
csi-attacher | k8s.gcr.io/sig-storage/csi-attacher |
kube-fencing-switcher | docker.io/kvaps/kube-fencing-switcher |
kube-fencing-controller | docker.io/kvaps/kube-fencing-controller |
ose-csi-external-attacher | registry.redhat.io/openshift4/ose-csi-external-attacher:v4.7 |
ose-csi-external-snapshotter-rhel8 | registry.redhat.io/openshift4/ose-csi-external-snapshotter-rhel8:v4.10 |
ose-csi-external-resizer-rhel8 | registry.redhat.io/openshift4/ose-csi-external-resizer-rhel8:v4.7 |
ose-csi-external-provisioner-rhel8 | registry.redhat.io/openshift4/ose-csi-external-provisioner-rhel8:v4.10 |
ose-csi-driver-registrar | registry.redhat.io/openshift4/ose-csi-driver-registrar:v4.3 |
Table: Image names with tags for side car containers
Image name | Tag | Required tag |
---|---|---|
csi-snapshotter | v6.0.1 | <IP address of custom registry>:<port number>/csi-snapshotter:v6.0.1 |
csi-provisioner | v3.2.1 | <IP address of custom registry>:<port number>/csi-provisioner:v3.2.1 |
csi-resizer | v1.1.0 | <IP address of custom registry>:<port number>/csi-resizer:v1.1.0 |
csi-node-driver-registrar | v2.1.0 | <IP address of custom registry>:<port number>/csi-node-driver-registrar:v2.1.0 |
csi-attacher | v3.1.0 | <IP address of custom registry>:<port number>/csi-attacher:v3.1.0 |
kube-fencing-switcher | v2.3.0 | <IP address of custom registry>:<port number>/kube-fencing-switcher:v2.3.0 |
kube-fencing-controller | v2.3.0 | <IP address of custom registry>:<port number>/kube-fencing-controller:v.2.3.0 |
ose-csi-external-attacher | v4.7 | <IP address of custom registry>:<port number>/ose-csi-external-attacher:v4.7 |
ose-csi-external-snapshotter-rhel8 | v4.10 | <IP address of custom registry>:<port number>/ose-csi-external-snapshotter-rhel8:v4.10 |
ose-csi-external-resizer-rhel8 | v4.7 | <IP address of custom registry>:<port number>/ose-csi-external-resizer-rhel8:v4.7 |
ose-csi-external-provisioner-rhel8 | v4.10 | <IP address of custom registry>:<port number>/ose-csi-external-provisioner-rhel8:v4.10 |
ose-csi-driver-registrar | v4.3 | <IP address of custom registry>:<port number>/ose-csi-driver-registrar:v4.3 |
You must pull these images, tag correctly, and subsequently push the tagged images to the custom registry. The commands are in the following format.
Pulling the image
docker pull <source from the above table>:<tag from the above table>
Correctly tagging the image
docker tag <source from the above table>:<tag from the above table> <Required tag from the above table>
Pushing the image
docker push <Required tag from the above table>
An example of commands for csi-snapshotter is as under -
docker pull k8s.gcr.io/sig-storage/csi-snapshotter:v6.0.1
docker tag k8s.gcr.io/sig-storage/csi-snapshotter:v6.0.1 <IP address of custom registry>:<port number>/csi-snapshotter:v6.0.1
docker push <IP address of custom registry>:<port number>/csi-snapshotter:v6.0.1
Run these commands on all the images.