-
Notifications
You must be signed in to change notification settings - Fork 40k
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
dynamiccertificates: denoise Kubelet logs by skipping removal of non-existent file watchers #126295
dynamiccertificates: denoise Kubelet logs by skipping removal of non-existent file watchers #126295
Conversation
staging/src/k8s.io/apiserver/pkg/server/dynamiccertificates/dynamic_cafile_content.go
Outdated
Show resolved
Hide resolved
…existent file watchers This commit updates the DynamicFileCAContent controller to skip the removal of non-existent file watchers. Previously, the controller attempted to remove a file watch even if it didn't exist, which resulted in a flood of error messages being logged in the Kubelet logs. Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
a8aab86
to
17ad4b3
Compare
/triage accepted |
LGTM label has been added. Git tree hash: bc54cfdf48d49776447e7ccad59016f4e5c6922b
|
/assign @deads2k |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, sohankunkerkar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
xref: https://issues.redhat.com/browse/OCPBUGS-36295
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This commit updates the DynamicFileCAContent controller to skip the removal of non-existent file watchers. Previously, the controller attempted to remove a file watch even if it didn't exist, which resulted in a flood of error messages being logged in the Kubelet logs.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Here's the Kubelet logs:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: