Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make admissionOperations backward compatible with previously deployed ModRules #109

Closed
vassilvk opened this issue Dec 15, 2022 · 1 comment · Fixed by #110
Closed

Make admissionOperations backward compatible with previously deployed ModRules #109

vassilvk opened this issue Dec 15, 2022 · 1 comment · Fixed by #110

Comments

@vassilvk
Copy link
Member

Upgrading to v0.18.0 introduces admissionOperation, which is an optional ModRule attribute defaulting to ["CREATE", "UPDATE"].
The issue is that the default set of operations is only set on ModRule deployment, essentially deactivating previously deployed ModRules.
@vassilvk vassilvk mentioned this issue Dec 15, 2022
Merged
@vassilvk
Copy link
Member Author

Hi @orbatschow,
FYI, please note the above issue, now resolved in v0.18.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make admissionOperations backward compatible with previously deployed… kubemod/kubemod
1 participant
@vassilvk