unrecognized arguments: --cluster-autoscaler-profile scan-interval=30s
See original GitHub issueDescribe the bug
Command Name
az aks create
Errors:
az: error: unrecognized arguments: --cluster-autoscaler-profile scan-interval=30s
To Reproduce:
az aks create \
--resource-group xyz \
--name xyz \
--node-vm-size Standard_F2s_v2 \
--nodepool-name xyz \
--node-count 1 \
--enable-cluster-autoscaler \
--min-count 1\
--max-count 3 \
--cluster-autoscaler-profile scan-interval=30s \
--location westeurope \
--enable-addons monitoring \
--generate-ssh-keys \
--service-principal xyz \
--client-secret xyz
Will result in above mentioned error.
If I simply omit --cluster-autoscaler-profile scan-interval=30s
cluster will be successfully created.
This option is suggested in documentation page: Set the cluster autoscaler profile when creating an AKS
az aks create \
--resource-group myResourceGroup \
--name myAKSCluster \
--node-count 1 \
--enable-cluster-autoscaler \
--min-count 1 \
--max-count 3 \
--cluster-autoscaler-profile scan-interval=30s
Furthermore, if I try to add scan-itnerval
option once the cluster was created as suggested in documentation: Set the cluster autoscaler profile on an existing AKS cluster
az aks update \
--resource-group xyz \
--name xyz \
--cluster-autoscaler-profile scan-interval=30s
I’ll get the same error:
az: error: unrecognized arguments: --cluster-autoscaler-profile scan-interval=30s
Expected Behavior
I would expect scan-interval
option which defines how often cluster is reevaluated for scale up or down to be enabled as suggested in official documentation.
Environment Summary
Linux-5.4.0-21-generic-x86_64-with-debian-bullseye-sid (Ubuntu 20.04)
Python 3.6.5
Installer: DEB
azure-cli 2.3.1
Additional Context
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Use the cluster autoscaler in Azure Kubernetes Service (AKS)
The above command creates an AKS cluster and defines the scan interval as 30 seconds for the cluster-wide autoscaler profile. The command also ......
Read more >Amazon EKS - User Guide
Reducing the scan interval. Using a low scan interval, such as the default setting of ten seconds, ensures that the Cluster Autoscaler.
Read more >Release Notes | Google Cloud CLI Documentation
Added --stack-type and --ipv6-access-type arguments to gcloud container clusters create command to support dual stack GKE clusters.
Read more >Spring Boot Reference Documentation
The following content is for you: Spring Application: SpringApplication. External Configuration: External Configuration. Profiles: Profiles. Logging: Logging ...
Read more >All configuration options - Quarkus
AWS Lambda Type Default
AWS Lambda Common Type Default
AWS Lambda Gateway REST API Type Default
Agroal ‑ Database connection pool Type Default
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@marwanad problem is that
libffi6
is not available in 20.04focal
repos, last Ubuntu release it was in is 19.04eoan
.However, out of sheer curiosity I downloaded libffi6 for 19.04 release, installed it and it worked.
After which I was able to add
--cluster-autoscaler-profile scan-interval=30s
option to my cluster.I created a feature request in regards to packaging issue: https://github.com/Azure/azure-cli/issues/13081
Thank you for your assistance and please feel free to close this issue.
Closing, and using the linked issue to track.