CKS: control plane certificates are never renewed or checked, and the stored kubeconfig isn't refreshed after upgrade

Ouverte
  • Quelque chose ne va pas ?
#14,650 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@bhouse-nexthop y travaille déjà.

Depuis le 9/11/2026.

  • #14651 par @bhouse-nexthop — ouverte

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
java, kubernetes
Domaine
backend-api-design, infrastructure

Piste de recherche

Start by tracing upgradeKubernetesCluster and getKubernetesClusterConfig, which the issue identifies as the upgrade and stored kubeconfig paths. Check how CKS reads and stores the control node’s kubeconfig, then inspect the related open pull request #14651 for work already underway. Done means refreshed kubeconfig data after certificate renewal and a decided approach for expiry checks and renewal.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

problem

CKS clusters are set up with kubeadm, which issues the control plane certificates (API server, front proxy, stacked etcd, and the client certificates in admin.conf, controller-manager.conf and scheduler.conf) for one year. The certificate authorities last ten years.

Nothing in CKS deals with that:

  1. No renewal. CKS never runs kubeadm certs renew, and there is no API to do it. kubeadm's own answer is "upgrade at least once a year", since kubeadm upgrade renews the certificates as a side effect. A cluster that isn't upgraded within a year stops working when the certificates expire: the API server rejects the controller manager, the scheduler and every admin client, and kubectl from CloudStack itself (/root/.kube/config on the control nodes) fails too.
  2. No expiry check. Nothing warns the operator before that happens. There's no alert and no event.
  3. The stored kubeconfig is not refreshed after an upgrade. getKubernetesClusterConfig returns the kubeConfigData cluster detail, which CKS only reads from the control node when the cluster starts. upgradeKubernetesCluster renews the certificates, admin.conf included, but the stored copy keeps the old admin certificate. Anyone who downloads the kubeconfig from CloudStack after an upgrade still gets a certificate that dies at the old expiry date. The same happens after renewing the certificates by hand.

Related: after an upgrade, /root/.kube/config on the control nodes, a copy of admin.conf that CKS uses for its own kubectl calls, also keeps the old certificate.

versions

main (and 4.22). The code involved hasn't changed in a long time, so earlier releases are affected too.

The steps to reproduce the bug
  1. Create a CKS cluster and leave it running.
  2. On a control node, run sudo /opt/bin/kubeadm certs check-expiration. Every leaf certificate expires one year after creation, and nothing in CloudStack reports it.
  3. Upgrade the cluster with upgradeKubernetesCluster. check-expiration now shows renewed certificates.
  4. Call getKubernetesClusterConfig and decode the client-certificate-data of the returned kubeconfig: its expiry is still the original one, a year after creation.
What to do about it?
  • Refresh the stored kubeconfig after an upgrade and after a renewal.
  • Check the certificate expiry periodically, and alert ahead of it (for example 60 and 30 days).
  • Add an API that renews the control plane certificates one control node at a time and restarts the control plane static pods.
  • Renew automatically, through the same path, some time before expiry (configurable).
Langage dominant
Java
Étoiles
3.1k
Forks
1.4k
Merge moyen
7 j 16 h
PR mergées (30 j)
15

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/cloudstack

Toutes les issues de apache/cloudstack

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.