You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kubernetes Version (kubectl): v1.23.10
kubeadm Version: v1.23.10
In a Kubernetes cluster deployed with kubeadm, a problem with an expired apiserver certificate has occurred a year after deploying a new node. The error is: x509: certificate has expired or is not yet valid: current time 2024-09-18T12:18:40Z is after 2024-09-10T12:29:33Z.
The error persists and indicates that the certificate is still expired as of the 10th, even though the kubeadm certs check-expiration command shows that all certificates should expire in at least a year.
What could be the cause of the problem, and what additional steps can be taken to resolve it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone,
Kubernetes Version (kubectl): v1.23.10
kubeadm Version: v1.23.10
In a Kubernetes cluster deployed with kubeadm, a problem with an expired apiserver certificate has occurred a year after deploying a new node. The error is:
x509: certificate has expired or is not yet valid: current time 2024-09-18T12:18:40Z is after 2024-09-10T12:29:33Z
.Steps Taken to Resolve (source):
The error persists and indicates that the certificate is still expired as of the 10th, even though the
kubeadm certs check-expiration
command shows that all certificates should expire in at least a year.What could be the cause of the problem, and what additional steps can be taken to resolve it?
Beta Was this translation helpful? Give feedback.
All reactions