VMware vSphere 7.0 with TanzuVMware vSphere Kubernetes ServicevSphere with TanzuTanzu Kubernetes Runtime
Issue/Introduction
This KB is written for advising on the following vSphere Supervisor certificates which are not included in the renewal performed by the certmgr script:
/etc/vmware/wcp/tls/authproxy-client.crt
/etc/vmware/wcp/tls/pinniped.crt
/etc/vmware/wcp/tls/vip.crt
/var/etcdmgr/signer/crt/wcp_node_bootstrapper
Certificates that are renewed by the certmgr script can be found by running the following certmgr script command while SSH into the VCSA:
Retrieve the Supervisor cluster ID:
./certmgr supervisors
View all certificates on the chosen Supervisor cluster ID, replacing "domain-c#:########-####-####-####-#############" with the desired Supervisor cluster's ID from above:
./certmgr certificates list -c domain-c#:########-####-####-####-#############
A list of vSphere Supervisor certificates can be found while directly SSH into a Supervisor control plane VM and performing the following find command:
However, this certmgr script does not renew the authproxy-client, pinniped, vip and wcp_node_bootstrapper certificates:
The /etc/vmware/wcp/tls/vip.crt also known as the Workload Platform Management certificate can be renewed through the steps in KB: Replace the Self-Signed vip.crt
/etc/vmware/wcp/tls/authproxy-client.crt and /etc/vmware/wcp/tls/pinniped.crt are managed and automatically renewed by the cert-manager controller in the Supervisor cluster.
It is currently not supported to use custom certificates for these certificates.
/var/etcdmgr/signer/crt/wcp_node_bootstrapper is only used on initial creation of a Supervisor cluster and does not need to be renewed.
All certificates are automatically renewed upon successful Supervisor cluster upgrade.
Resolution
A list of vSphere Supervisor certificates can be found while directly SSH into a Supervisor control plane VM and performing the following find command:
However, this certmgr script does not renew the authproxy-client, pinniped, vip and wcp_node_bootstrapper certificates.
authproxy-client.crt and pinniped.crt
The /etc/vmware/wcp/tls/authproxy-client.crt is an internally generated client certificate which allows for nginx to make successful requests to authproxy.
The /etc/vmware/wcp/tls/pinniped.crt is an internally generated CA certificate used for establishing trust between nginx and pinniped.
These certificates are managed by the cert-manager controller in the Supervisor cluster and are expected to be automatically rotated before expiration by the cert-manager controller accordingly.
Supervisor OIDC Federation requires both certificates.
If Pinniped is not used in the environment, these certificates are also not used but the certificates will still be generated and renewed regardless.
It is currently not supported to use custom certificates for these certificates.
vip.crt - Workload Platform Management
The /etc/vmware/wcp/tls/vip.crt also known as the Workload Platform Management certificate can be renewed through the steps in KB: Replace the Self-Signed vip.crt
wcp_node_bootstrapper
/var/etcdmgr/signer/crt/wcp_node_bootstrapper is only used on initial creation of a Supervisor cluster and does not need to be renewed.