[CapacityScheduling] Proposal to Add Warning and Restriction for Multiple elasticQuotas in One Namespace

[Gekko0114]

It's currently assumed that developers will create only one elasticQuota for each namespace.
However, it is possible to create multiple elasticQuotas in a single namespace.

I would like to propose two changes to address this issue:

1. We should add a warning not to create multiple elasticQuotas in a single namespace in README.md
2. If possible, we should restrict the creation of only one elasticQuota per namespace

If this propose seems reasonable, I would be happy to work on implementing these changes.

[Gekko0114]

/assign

I will fix it by using validationwebhook or similar functions after completing this PR #527.

[Huang-Wei]

@Gekko0114 we're not deciding to introduce the complexity of having a validationwebhook yet.

I want to hold this until it's a must-have. But it's good to keep it as a good-to-have list that relies on webhook.

[Gekko0114]

@Huang-Wei
Thank you for your response!
I agree that introducing a validationwebhook can make repository more complicated.
However, with the current implementation, it is possible to create multiple ElasticQuota in a single namespace, but only one of them will actually work.

This could be confusing for developers. In my opinion, we should introduce a validationwebhook. Please let me know when the policy for scheduler-plugins is decided!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.