TLS certificate expires
A serving or client certificate reaches its notAfter date.
ImpactCalls fail on TLS, often across the whole cluster for a control plane certificate
Can it be seen coming?Yes
RupturaPlanned
How to detect it
Expiry inside a warning window.
Metrics and signals to watch:
certificate notAfter in Secretsapiserver_client_certificate_expiration_seconds
Can you see it coming?
Yes Precursor: The expiry date itself, weeks ahead.
What it hits next
every client of the certificate.
What to do
Renew the certificate and check its automation.
Sources
- kubernetes-mixin KubeClientCertificateExpiration
- kubernetes-mixin KubeletClientCertificateExpiration
Where Ruptura stands
This failure is on the Ruptura roadmap. It is not reported yet.
Related failures
- OpenShift cluster operator degraded
- Machine config pool degraded
- OLM operator install fails
- Metrics target down
See it coming instead of reading about it
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub