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 it possible to change API request frequency for create/delete vm api calls #706

Open
bg502 opened this issue Apr 20, 2022 · 1 comment
Labels
area/quality Output qualification (tests, checks, scans, automation in general, etc.) related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) needs/planning Needs (more) planning with other MCM maintainers priority/3 Priority (lower number equals higher priority)

Comments

@bg502
Copy link

bg502 commented Apr 20, 2022

/area quality
/kind enhancement
/priority 3

What would you like to be added:
MCM needs to have a way to configure API requests frequency.

Why is this needed:
On failure to create an instance, MCM makes a lot of API calls to the instance provider server, exhausting API request limits. There is already a similar issue, requesting an exponential back-off timer after a failure.

Yet, I believe the ability to change the timer manually or simply increase it during the problem (which can last if, for example, the cloud provider does not have the necessary capacity at the moment) is also an important one.

@bg502 bg502 added the kind/enhancement Enhancement, improvement, extension label Apr 20, 2022
@gardener-robot gardener-robot added area/quality Output qualification (tests, checks, scans, automation in general, etc.) related priority/3 Priority (lower number equals higher priority) labels Apr 20, 2022
@himanshu-kun himanshu-kun added priority/2 Priority (lower number equals higher priority) priority/3 Priority (lower number equals higher priority) and removed priority/3 Priority (lower number equals higher priority) priority/2 Priority (lower number equals higher priority) labels May 24, 2022
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 21, 2022
@himanshu-kun
Copy link
Contributor

himanshu-kun commented Feb 21, 2023

Post-grooming discussion

@himanshu-kun himanshu-kun added needs/planning Needs (more) planning with other MCM maintainers and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 21, 2023
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Oct 31, 2023
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/quality Output qualification (tests, checks, scans, automation in general, etc.) related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) needs/planning Needs (more) planning with other MCM maintainers priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

3 participants