-
Notifications
You must be signed in to change notification settings - Fork 61
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
make detectionMode configurable per namespace #743
Comments
My idea would be to allow for all features (namespace, detection, unchanged, child, maybe alerting(?)) to enable them for certain namespaces. I see two options
Both have the problem of only working in those namespace that are within the namespace validation set, which may be unclear. I think I tend slightly toward the former solution since I personally dislike the idea of many labels on resources, but that preference is only very weak. I could also implement both methods, and allow the user to choose. Any thoughts @xopham @phbelitz ? |
Discussed in #691
Originally posted by albertovmware June 17, 2022
I think that it could be good to block unsigned images in a specific namespace and use detection mode on other namespaces.
When i use the namespace validation I can select ignore & validate, maybe adding another tag in the validate mode, like "validate_warm" could solve it.
Other option can be allowing detectionMode per namespace using tags.
Maybe it's possible to do it and I'm missing something...
If anyone can suggest anyway to do that, it will be appreciated
Thanks
The text was updated successfully, but these errors were encountered: