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.

Sign up for GitHub

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

Jump to bottom

Deal with paused machineDeployments #189

Open
himanshu-kun opened this issue Mar 21, 2023 · 2 comments
Open

Deal with paused machineDeployments #189

himanshu-kun opened this issue Mar 21, 2023 · 2 comments
Labels
area/auto-scaling Auto-scaling (CA/HPA/VPA/HVPA, predominantly control plane, but also otherwise) related area/control-plane Control plane related area/robustness Robustness, reliability, resilience 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/2 Priority (lower number equals higher priority)
Milestone
2023-Q2

Comments

@himanshu-kun
Copy link

What would you like to be added:

Autoscaler should be able to ignore paused machineDeployments.
Currently MCM offers a feature where a user can pause the machineDeployment during rolling update. The integration of this functionality with gardener is still underway github.com/gardener/gardener/issues/7485.
As part of this integration it is essential that relevant changes are made to autoscaler so that its aware of paused machineDeployments.

Why is this needed:
To disallow unwanted scaling operation on a machineDeployment which is paused by user for reasons like service unavailability during rolling update of the machineDeployment.
@himanshu-kun himanshu-kun added area/robustness Robustness, reliability, resilience related kind/enhancement Enhancement, improvement, extension area/control-plane Control plane related area/auto-scaling Auto-scaling (CA/HPA/VPA/HVPA, predominantly control plane, but also otherwise) related priority/1 Priority (lower number equals higher priority) needs/planning Needs (more) planning with other MCM maintainers labels Mar 21, 2023
@himanshu-kun
Copy link
Author

A proposed solution could be found here

@himanshu-kun himanshu-kun added priority/2 Priority (lower number equals higher priority) and removed priority/1 Priority (lower number equals higher priority) labels Mar 21, 2023
@himanshu-kun himanshu-kun modified the milestone: 2023-Q2 Mar 21, 2023
@himanshu-kun
Copy link
Author

/milestone 2023-Q2

@gardener-robot gardener-robot added this to the 2023-Q2 milestone Mar 21, 2023
@ashwani2k ashwani2k mentioned this issue Aug 4, 2023
Open
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 28, 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 Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/auto-scaling Auto-scaling (CA/HPA/VPA/HVPA, predominantly control plane, but also otherwise) related area/control-plane Control plane related area/robustness Robustness, reliability, resilience 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/2 Priority (lower number equals higher priority)
Projects
None yet
Milestone
2023-Q2
Development

No branches or pull requests
2 participants
@gardener-robot @himanshu-kun