Skip to content

Cannot set expander with multiple parameter in aks cluster autoscaler profile #29379

Description

@JoeyC-Dev

Describe the bug

Cannot set expander with multiple parameter in aks cluster autoscaler profile

Related command

az aks update -n ${aks} -g ${rG} -o none \
--cluster-autoscaler-profile expander=priority,least-waste

Errors

'least-waste' is an invalid key for cluster-autoscaler-profile. Valid keys are balance-similar-node-groups, expander, max-empty-bulk-delete, max-graceful-termination-sec, max-node-provision-time, max-total-unready-percentage, new-pod-scale-up-delay, ok-total-unready-count, scan-interval, scale-down-delay-after-add, scale-down-delay-after-delete, scale-down-delay-after-failure, scale-down-unneeded-time, scale-down-unready-time, scale-down-utilization-threshold, skip-nodes-with-local-storage, skip-nodes-with-system-pods.

Issue script & Debug output

I don't think this is needed.

Expected behavior

It should be supported to be configured via azure-cli.

Environment Summary

{
  "azure-cli": "2.61.0",
  "azure-cli-core": "2.61.0",
  "azure-cli-telemetry": "1.1.0",
  "extensions": {
    "ai-examples": "0.2.5",
    "ml": "2.26.1",
    "ssh": "2.0.3"
  }
}

Additional context

In the official FAQ, it is stated that multiple parameters are supported for expander. E.g: --expander=priority,least-waste.
src: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-expanders

It is also possible to be done via ARM template. And I can see the result:
image

az aks show -n ${aks} -g ${rG} --query autoScalerProfile.expander
"priority,least-waste"

However, it is not possible to be done via az-cli for now as it needs to inlcude ,.

Also tried the following command, no use:

joey [ ~ ]$ az aks update -n ${aks} -g ${rG} -o none \
--cluster-autoscaler-profile expander=priority,expander=least-waste
joey [ ~ ]$ az aks show -n ${aks} -g ${rG} --query autoScalerProfile.expander
"least-waste"

Alternative solution considered:
Support json format as input.

Metadata

Metadata

Assignees

No one assigned

    Labels

    AKSaz aks/acs/openshiftAuto-AssignAuto assign by botAuto-ResolveAuto resolve by botService AttentionThis issue is responsible by Azure service team.act-observability-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions