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.

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

feat: added require-resource-quota for multitenancy-benchmark category #117

Merged
merged 5 commits into from
Feb 25, 2024

Conversation

fykaa
Copy link
Contributor

@fykaa fykaa commented Feb 21, 2024

Policy Description

require-resource-quota: Namespace resource quotas should be used to allocate, track and limit the number of objects, of a particular type, that can be created within a namespace. In cases such as multi-tenancy where new Namespaces must be fully provisioned before they can be used, it may not be easy to declare and understand if/when the Namespace is ready. Having a policy which defines all the resources which are required for each Namespace can assist in determining compliance. This policy, expected to be run in background mode only, performs a Namespace check to ensure that all Namespaces have a ResourceQuota. Additional rules may be written to extend the check according to needs.

Policy Category

Multitenancy Benchmark

@fykaa fykaa requested review from nsathyaseelan and removed request for nsathyaseelan February 23, 2024 16:59
@anusha94
Copy link
Collaborator

@fykaa Would be nice to have a README.md for all multitenancy policies, like we have for kyverno-json policies. I'm merging this now, the README can be in a follow-up PR.

@anusha94 anusha94 merged commit c9f34af into nirmata:main Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants