feat: pod reload on configmaps and falco separated configmaps #2057
+779
−196
Conversation
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
mjnagel
reviewed
Oct 24, 2025
| @@ -1,14 +1,14 @@ | |||
| --- | |||
| title: Secret Pod Reload | |||
| title: Resource Pod Reload | |||
There was a problem hiding this comment.
Let's make sure to add a doc redirect to the docs site since this one has been linked in release notes, etc. I also wonder if it makes more sense to just call it "pod reloading"?
There was a problem hiding this comment.
Yeah tracking the redirect, put up a PR for that. I like the idea of calling the doc Pod Reload, simpler, more straightforward.
There was a problem hiding this comment.
Let's rename the file to match, which should make the docs PR correct 😄
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Previously all Falco configmaps for rules were combined into a single configmap, this raised concerns that over time as those rules change the configmap could become too large. This PR will separate each ruleset out into its own configmap.
Additionally, when Falco ruleset changes and we update a configmap we want our pods to reload so that Falco starts using that new configmap. Previously uds core only supported pod reloading on secret changes, this PR will expand that functionality to work with configmaps as well as secrets.
Related Issue
Fixes #1972
Type of change
Checklist before merging