-
Notifications
You must be signed in to change notification settings - Fork 2k
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
introduce custom-resources-only flag ... #1813
Conversation
We could add this flag, I'd expect v3.0 to overhaul all the config flags and move us towards an allowlist/denylist model. |
Agreed, having this flag would be a great addition to ksm. In v3, we can definitely improve the existing flags to make it easier since the current list kind of grew on us over time, but I wouldn't block that effort on that. It would be great to be able to split ksm and the crd version of ksm already in v2. |
@bavarianbidi do you have plans to get back to this change? We could try getting it into the next release. |
2faf8a8
to
3f6d253
Compare
3f6d253
to
8f34947
Compare
👋 sorry for the late reply 🙈 |
8f34947
to
fd8ae6d
Compare
... to only monitor all known custom-resource configurations instead of listing each of them explicitly Signed-off-by: Mario Constanti <mario@constanti.de>
fd8ae6d
to
53af116
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold
Looking forward to start using this feature, thank you @bavarianbidi :) /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bavarianbidi, dgrisonnet, mrueg 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 |
... to only monitor all known custom-resource configurations instead of
listing each of them explicitly
Signed-off-by: Mario Constanti mario@constanti.de
What this PR does / why we need it:
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1778