fix(core): Use k8s informers to watch host and network policies#2598
Merged
AryanBakliwal merged 1 commit intoMay 29, 2026
Merged
Conversation
91abf42 to
1471e1d
Compare
rksharma95
requested changes
May 14, 2026
rksharma95
left a comment
Collaborator
There was a problem hiding this comment.
LGTM, just a suggestion commented inline.
1471e1d to
2c868c5
Compare
rksharma95
approved these changes
May 14, 2026
2c868c5 to
37cac69
Compare
Signed-off-by: Aryan Bakliwal <[email protected]>
37cac69 to
a408505
Compare
Aryan-sharma11
approved these changes
May 29, 2026
This file contains hidden or 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
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.
Purpose of PR?:
When running in K8s mode, after around 30-40 min. of deploying we get these logs
Even though the CRDs are present in the cluster. Cause explained here.
This PR fixes this by using K8s informers for watching host and network policies, similar to watching cluster security policies.
Also fixes #1057
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered:
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>