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
Managing licenses
While installing InfoScale in an OpenShift or Kubernetes environment, you apply licenses. You select the license edition and optionally enter the IP address of the VIOM server in your environment.
The license server IP address can be updated to license_cr.yaml subsequently, if not entered while installing. Edit <path>/license_cr.yaml and enter IP address of the VIOM server for licenseServer. After updating the yaml, run kubectl/oc apply -f <path>/license_cr.yaml to apply the license with the updated IP address of the VIOM server.
After the IP address of the VIOM server is specified and the license is applied, you can check the status. Run kubectl describe license <path>/license_cr.yaml. Review the License Server Status message with the following table. You can initiate appropriate action on the basis of the message.
Table: License status message with the meaning
Message.. | Means.. |
|---|---|
Active | Connected successfully. |
License Server is not registered with Veritas | VIOM Server is not registered with Veritas. |
Subscription License has expired | Trial period of the license is over. |
Subscription License not available on License Server | License is not available on the VIOM server to which the connection is successful. |
Subscription License overused. Kindly check the usage limit. | Exceeded limits of the license edition. |
Error getting License Server status | VIOM Server is successfully connected, but does not return any message to the licensing operator pod. |
Connection Error : Not Connected with License Server | Licensing operator pod is unable to connect to the VIOM server on the specified IP address. |