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
The cache is not functioning properly, resulting in a null namespace. Logs have been attached for reference.
Cluster certificates were updated, but the etcdadmcontroller pod continued reporting them as invalid.
The log error message itself is clear and includes valid dates, yet the pod still flagged the certificates as invalid. This caused the kube-apiserver to become non-responsive for a period.
We need to figure out how to get rid of the specific errors from the first part and figure our why restarting the pods would cause the certificate to be counted.
The text was updated successfully, but these errors were encountered:
https://t.corp.amazon.com/P167063564
There are two issues called out:
The log error message itself is clear and includes valid dates, yet the pod still flagged the certificates as invalid. This caused the kube-apiserver to become non-responsive for a period.
We need to figure out how to get rid of the specific errors from the first part and figure our why restarting the pods would cause the certificate to be counted.
The text was updated successfully, but these errors were encountered: