Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate issue with getting etcdadmcluster object due to unknown namespace #9079

Open
vivek-koppuru opened this issue Dec 14, 2024 · 0 comments
Milestone

Comments

@vivek-koppuru
Copy link
Member

https://t.corp.amazon.com/P167063564

There are two issues called out:

  1. The cache is not functioning properly, resulting in a null namespace. Logs have been attached for reference.
  2. 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.

@vivek-koppuru vivek-koppuru added this to the v0.22.0 milestone Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant