Kubeconfig Invalidated after Kubernetes Cluster Upgrade of PMK Clusters

Problem

• The kubeconfig which was working before upgrade no longer works after the upgrade with an error like below

xxxxxxxxxx

x509: certificate signed by unknown authority

Environment

• Platform9 Managed Kubernetes - v5.6 and Higher

Answer

• Platform9 is aware about the issue and an internal bug with ID: PMK-6421 has already been reported for this issue.

Cause

• Whenever the Cluster CA is rotated, the kubeconfig gets invalidated. This is the expected behavior as per product design.
• Cluster CA is valid for 10 years and is rotated every 5 years. So after every 5 years, the kubeconfig needs to be rotated/replaced.
• On subsequent cluster upgrades, as long as the CA isn’t rotated again, the older/existing kubeconfig will remain valid between version upgrades.

Additional Information

• Reach out to Platform9 Support with the aforementioned Bug ID for more information.