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
k8s: Use Resource[*Pod] in pod watcher for the local pod watching #26181
Merged
joestringer
merged 1 commit into
cilium:main
from
joamaki:pr/joamaki/pod-watcher-use-resource
Jun 15, 2023
Merged
k8s: Use Resource[*Pod] in pod watcher for the local pod watching #26181
joestringer
merged 1 commit into
cilium:main
from
joamaki:pr/joamaki/pod-watcher-use-resource
Jun 15, 2023
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
maintainer-s-little-helper
bot
added
the
dont-merge/needs-release-note-label
The author needs to describe the release impact of these changes.
label
Jun 13, 2023
joamaki
added
the
release-note/misc
This PR makes changes that have no direct user impact.
label
Jun 14, 2023
maintainer-s-little-helper
bot
removed
the
dont-merge/needs-release-note-label
The author needs to describe the release impact of these changes.
label
Jun 14, 2023
/test |
bimmlerd
reviewed
Jun 15, 2023
Now that Resource[*Pod] has been added as a shared resource and it is seeing use from multiple modules, refactor the pod watcher to also use it for the normal case of watching just the local pods. The "handover" case of watching all pods still creates a separate informer, but this should affect very small set of deployments. Signed-off-by: Jussi Maki <jussi@isovalent.com> Signed-off-by: David Bimmler <david.bimmler@isovalent.com>
bimmlerd
force-pushed
the
pr/joamaki/pod-watcher-use-resource
branch
from
June 15, 2023 09:23
b9679af
to
6c6aefc
Compare
/test |
Labelled this a |
bimmlerd
added
area/daemon
Impacts operation of the Cilium daemon.
sig/k8s
Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.
kind/performance
There is a performance impact of this.
sig/agent
Cilium agent related.
labels
Jun 15, 2023
AFAIK Nate is on PTO - I'll try unassigning and rerequesting sig-k8s. |
aanm
approved these changes
Jun 15, 2023
maintainer-s-little-helper
bot
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jun 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/daemon
Impacts operation of the Cilium daemon.
kind/bug
This is a bug in the Cilium logic.
kind/performance
There is a performance impact of this.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
sig/agent
Cilium agent related.
sig/k8s
Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.
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.
Now that Resource[*Pod] has been added as a shared resource and it is seeing use from multiple modules, refactor the pod watcher to also use it for the normal case of watching just the local pods.
The "handover" case of watching all pods still creates a separate informer, but this should affect very small set of deployments.