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

Add Parameter to checkcapacity ProvisioningRequest that disables CA's retry mechanism #7495

Open
PBundyra opened this issue Nov 14, 2024 · 3 comments · May be fixed by #7496
Open

Add Parameter to checkcapacity ProvisioningRequest that disables CA's retry mechanism #7495

PBundyra opened this issue Nov 14, 2024 · 3 comments · May be fixed by #7496
Assignees
Labels
area/cluster-autoscaler kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@PBundyra
Copy link

Which component are you using?:
Cluster-autoscaler

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

If the checkcapacity ProvisioningRequest cannot be provisioned, it waits for backoff time before being retried. From the perspective of integration with Kueue, this time is wasteful as we block quota on Kueue's side, even it's not actively used.

Describe the solution you'd like.:
Add ProvisioningRequest Parameter that disables retry mechanism in CA. If the Parameter is present and the request cannot be provisioned it should be marked as Failed=True instead of Provisioned=False

Describe any alternative solutions you've considered.:
Add flag to the CA that disables retry mechanism. However we need more granular solution, because of different nature of some workloads - depending on a workload users are willing to block(or not) quota

Additional context.:

@PBundyra PBundyra added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 14, 2024
@PBundyra
Copy link
Author

/assign

@adrianmoisey
Copy link
Member

/area cluster-autoscaler

@Shubham82
Copy link
Contributor

/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cluster-autoscaler kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants