Veritas InfoScale™ for Kubernetes Environments 8.0.330 - 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
- 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
About InfoScale and container platform upgrades
Upgrading InfoScale and container platforms is a two-step process. When new kernel versions and operating system versions are available, you first upgrade InfoScale and then upgrade the operating system. The current process is takes up more time and involves stopping and restarting all the services.
This release supports a more efficient upgrade process wherein both the InfoScale and the container platform operating system (OS) version upgrades are combined and can be performed in a seamless manner. This combined upgrade workflow is supported via a new configuration parameter named combine-upgrade
. You can add this parameter under annotations in the yaml file and then enable this parameter before proceeding with the InfoScale and OS upgrade.
Before you perform the combined InfoScale and container platform OS upgrade, you must first perform the operator based upgrade using OLM. For instructions, see On an OpenShift cluster.
The combined upgrade process flow is as follows:
Add the
combine-upgrade
parameter under annotations in theCR.yaml
file and set it to enabled on the InfoScale cluster CR while updating InfoScale. This ensures that the InfoScale pods are upgraded only once and during the OS upgrade.Ensure that the cluster is in running state and then start the InfoScale upgrade. This upgrades the CSI, fencing, toolset pods, and the SDS daemonset. The pod upgrade is delayed until the OS upgrade.
Once the InfoScale upgrade is complete, the phase is set to
OS-upgrade-pending
and the following event is logged:Type Reason Age From Message ---- ------ ---- ---- ------- Normal SDS pods will be updated as part of OS upgrade, 9m22s InfoScaleCluster Completed SDS daemonset update:
You can now proceed with the container platform upgrade. The InfoScale cluster phase changes to
OS-upgrade
.After the OS upgrade is complete, the cluster phase is set to
running
and the version update reflects in the status of the cluster.The following event is logged:
"Normal SDS pod update: 9m22s InfoScaleCluster Completed".
The
combine-parameter
annotation is reset to the default value of disabled again.
Note:
Do not change the annotation value of the combine-upgrade
parameter when the upgrade is in progress.
Manually edit the CR.yaml and add the following entry under annotations:
infoscale.veritas.com/combine-upgrade: enabled
You can also edit the yaml from the web console, switch to the yaml view to modify the yaml file.
To enable this parameter, run the following command:
# oc annotate infoscaleclusters -n infoscale-vtas infoscalecluster-qa "infoscale.veritas.com/combine-upgrade"="enabled" --overwrite