Veritas InfoScale™ for Kubernetes Environments 8.0.300 - 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
- Creating multiple InfoScale clusters
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Removing and adding back nodes to an Azure RedHat OpenShift (ARO) cluster
- Installing Veritas 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
- 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
- Creating ephemeral volumes
- 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
- Migrating applications to InfoScale
- Troubleshooting
Cert Renewal related
If Prometheus is configured and if after the external CA certificate is renewed, the pod monitor fails to come up. Delete the prometheus cert secret followed by deletion of all pods in the monitored namespace. Prometheus pods then come up.
If the following error message is logged -
x509: certificate has expired or is not yet valid: current time <timestamp1> is after <timestamp2>
If you are using an External CA certificate and the certificate has expired. See 'Renewing with an External CA certificate' and renew the certificate.
If you are using a self-signed CA, delete the infoscale-CA secret and wait for 10 minutes. Delete the secrets of all the client certificates.
If one of the following error messages is logged -
error:veritas:tls parseCertsCertificate expired :/etc/vx/<component name>/certs/tls.crtor
tls : bad certificate
If you are using an External CA certificate and the certificate has expired. See 'Renewing with an External CA certificate' and renew the certificate. If the certificate has not expired, delete all secrets of the client certificates,
If you are using a self-signed CA and the certificate has expired, delete the infoscale-CA secret and wait for 10 minutes. Delete the secrets of all the client certificates. If the certificate has not expired, delete the secrets of all the client certificates.