Veritas InfoScale™ for Kubernetes Environments 8.0.300 - 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
- 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
- Migrating applications to InfoScale
- Troubleshooting
Renewing with an external CA certificate
External CA certificates typically get renewed a few months before the validity end date. A cluster administrator re-creates the new certificates and populates the InfoScale cluster.
The new CA certificates can then be applied before the validity end date, before the earlier certificates expire.
When the external certificate is issued by the intermediary of the CA and the issuer knows the intermediary, the content of tls.crt
is a resulting certificate followed by a certificate chain. The certificate chain does not include a root CA certificate, as it is stored in ca.crt
.
For InfoScale the external CA certificate is valid for 12 months and as an Administrator, you can initiate its renewal after the eighth month.
Note:
Self-signing certificate is automatically renewed without any intervention. Validity of the self-signing certificate is four months and it is automatically renewed in the third month. However, external CA certificate needs to renewed.
Complete the following steps, ensuring that NTP is synchronized across nodes.
Run the following commands to renew the CA certificate.
Note:
This is an example of cfssl tool. You can also use any other tool to renew CA certificates. Refer to the procedure of that tool.
For generating the certificate.
cfssl gencsr -key /infoscale-ca-key.pem /csr_config.json | cfssljson -bare infoscale-ca
For signing the certificate.
cfssl sign -ca /etc/kubernetes/pki/ca.crt -ca-key /etc/kubernetes/pki/ca.key -hostname kubernetes -config ./vxconfig.json -profile cluster ./infoscale-ca.csr | cfssljson -bare infoscale-ca
Run the following command to generate the new secrets.
sh gen-cert
Run the following command to update the new
infoscale-ca
secret with renewedinfoscale-ca.pem
.kubectl apply -f custom-ca.yaml
Wait for upto five minutes.
Now you need to delete secrets of the following certificates.
infoscale-sds-rest-tls-cert-<value>
infoscale-csi-tls-cert
infoscale-fencing-tls-cert
iso-tls-cert
webhook-tls-cert
lico-tls-cert
Run the following command to delete secrets of these certificates.
kubectl delete secret -n infoscale-vtas <certificate name>
To enable encryption, perform steps listed in Configuring InfoScale to enable transfer of keys again.
After these certificates are deleted, the cert-manager automatically re-creates the new certificates. Wait for 15 minutes.
Note:
If DR is configured, ensure that you run these commands on the secondary site immediately after running these commands on the primary site.