Azure / Azure/aksArc

Allow scaling of workload clusters if there are critical updates available.

Open
#279 1 comment 0 reactions 0 assignees View on GitHub
Enhancement
Dominant language
PowerShell
Stars
118
Forks
63
PR merge metrics
No merged PRs in 30d

Description

**Title**: Allow scaling of workload cluster nodepools if there are critical updates available.

**Description**: I wanted to scale up nodepools of a workload cluster with `Set-AksHciNodePool -clusterName -name -count ` and got stopped by an error message to do a critical upgrade first.
![image](https://user-images.githubusercontent.com/6702311/206775875-3e7f1c42-fe57-4315-bf7f-8bd7019be2a9.png)

It would be nice to allow nodepool scaling if there are any critical upgrades available but not installed yet. In case of running out of resources, being forced to do a cluster upgrade first can cause serious trouble. In situations where peak loads are coming in not being able to scale up nodespools because updates had been published recently can be an unpleasant surprise.

Contributor guide

Open the contributing guide

Research direction

Start with the Set-AksHciNodePool command path, especially the nodepool scaling flow that currently blocks when critical updates are available. Reproduce the reported case with a workload cluster and an available critical update, then verify that changing the nodepool count succeeds without first installing the update.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, kubernetes, powershell
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.