Turn off CNP node status GC when CNP status updates are disabled. #24390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CNP Node Status GC was still running in cilium-operator even though by default CNP Node Status updates were disabled. This GC periodically made unnecessary API calls (one call per 10 policies) to k8s apiserver, which were going directly to underlying Etcd. Signed-off-by: Marcel Zieba <marcel.zieba@isovalent.com>
marseel
added
the
release-note/minor
squeed
approved these changes
Mar 16, 2023
|
/test |
maintainer-s-little-helper
bot
added
the
ready-to-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CNP Node Status GC was still running in cilium-operator even though by default CNP Node Status updates were disabled.
This GC periodically made unnecessary API calls (one call per 10 policies) to k8s apiserver, which were going directly to underlying Etcd.