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

Make CRDs namespaced scope #1285

Closed
dmarquez-splunk opened this issue Apr 22, 2024 · 2 comments
Closed

Make CRDs namespaced scope #1285

dmarquez-splunk opened this issue Apr 22, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@dmarquez-splunk
Copy link

What problem are you facing?

As a platform provider we would like to enforce quotas on the number of aws resources a team can have provisioned at any given time. Cluster scoped CRDs makes this tough as we cannot write quotas on a per-namespace basis. Can we make the CRDs namespaced scope so that we can enforce resource quotas on a per-namespace basis?

@dmarquez-splunk dmarquez-splunk added the enhancement New feature or request label Apr 22, 2024
@blakeromano
Copy link
Contributor

I think this is an issue with Crossplane not necessarily the AWS provider specifically. There is lots of other ways you can do this though without this enhancement.

You could use a validating webhook to validate based on label that a team has not met a quota and use label based queries to validate that a specific namespace has not violated your quota as one way to solve this problem.

Folks with more knowledge of the underlying mechanics of Crossplane can probably also describe the problem in a bit more detail but my assumption is this probably would not change.

@jeanduplessis
Copy link
Collaborator

Blake is correct, this isn't specific to this provider and is a topic that belongs in Crossplane.
@dmarquez-splunk I'm going to close this issue for now and suggest you have a look at maybe commenting on this open issue in crossplane-runtime: crossplane/crossplane-runtime#251

@jeanduplessis jeanduplessis closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants