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

[Feature] Force Drain and Force Reimage #4803

Open
kaarthis opened this issue Feb 19, 2025 · 1 comment
Open

[Feature] Force Drain and Force Reimage #4803

kaarthis opened this issue Feb 19, 2025 · 1 comment
Assignees
Labels
feature-request Requested Features Upgrade

Comments

@kaarthis
Copy link
Contributor

CX ran their workload, it's all done. None of the running pods are important at this point
CX cannot surge any node (no more GPU, or no more capacity, etc.)
CX do not want any node to be deleted (because they may not be able to create a new one after one is deleted, as the available capacity could be reclaimed by others).
CX want everything to be upgraded as fast as possible.

Essentially requesting an upgrade by force draining / Reimaging in place without consideration of surge capacity or Pods.

@bmoore-msft
Copy link
Contributor

I might suggest an edit to the last sentence in the OP...

An API to request an upgrade and immediate reimage without factoring in any cordon/drain/pdb. The node would be immediately reimaged and all nodes could be immediately reimaged in parallel. For example:

POST https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg1/providers/Microsoft.ContainerService/managedClusters/clustername1/forceReimage?api-version=2024-10-01

{
  "ignorePDB": true
}

Could be called on the managedCluster resource or an individual agentPool.

Where the POST body is there primarily as an "are you sure?" due to the disruptive nature of the operation. The purpose as mentioned in the OP is to upgrade as quickly as possible without relinquishing any nodes/vms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Requested Features Upgrade
Development

No branches or pull requests

4 participants