-
Notifications
You must be signed in to change notification settings - Fork 209
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
Provide example gatekeeper policies #1188
Comments
This issue has been automatically marked as stale because it has not had activity in 60 days. It will be closed if no further activity occurs. Thank you! |
I also consider this quite important to use the operator in a somewhat secure manner. Even with #1173 I might want to have gatekeeper rules just to uncover configuration mistakes. |
Issue still active. |
This is still something we're tracking to do |
We're still interested in doing this |
We're still interested in this. |
We still are interested in doing this |
Still interested in doing this. We would also be willing to accept contributions from the community if they have sample policies that they're already using in production. |
No change from the above. |
It would be great for multi-tenant clusters to have example (and supported) gatekeeper policies that enable namespace-based ownership of the resources, e.g. you can only access resources from Resource Groups with names dervived from your namespace using some conventions.
This is an alternative approach to: #1173
The text was updated successfully, but these errors were encountered: