Closed shm007g closed 5 years ago
Thanks for reporting this.
You can get latest version support table via command:
az aks get-versions -l chinaeast2 -o table
For 'auto-scale', it relies on VMSSPreview
feature, which is still a preview feature in azure global
, see doc.
azure china
doesn't support preview features for now. You can try azure global
if you would like to try preview features.
@karataliu Thanks for you reply. So, cluster auto-scale not available in Azure China AKS Private Preview? Am I right? If so, I may try acs-engine instead.
Thanks.
Yes, that's correct.
Besides, acs-engine
has renamed to aks-engine, you can redirect to the new project.
Thanks for your consideration.
@karataliu Thanks. I want to know if cluster autoscaler could be implemented with aks-engine/acs-engine? Where should I start with?
Thanks.
By the way, does AKS global support cluster autoscaler with vmss? When will this feature ship to china?
I want to know if cluster autoscaler could be implemented with aks-engine/acs-engine? Where should I start with?
@shm007g
VM Scale Set cluster example
in the doc@andyzhangx @karataliu Thanks.
Thanks for reporting this.
You can get latest version support table via command:
az aks get-versions -l chinaeast2 -o table
For 'auto-scale', it relies on
VMSSPreview
feature, which is still a preview feature inazure global
, see doc.azure china
doesn't support preview features for now. You can tryazure global
if you would like to try preview features.
You said VMSSPreview is a preview feature even in azure global. But I created a cluster scalable k8s cluster with acs-engine(0.25.3) + k8s(1.12) based on VMSS in Azure China
!
So, this VMSSPreview function should be ok in china to make my k8s CA working.
Am i wrong?
Hi @shm007g, az aks update --update-cluster-autoscaler
command(autoscaler integrated with AKS) is only for AKS and only work with AKS VMSSPreview, it's easier to use;
while if you use aks-engine, autoscaler works with both vmss and standard vmtype, but you need to deploy autoscaler by yourself and configure a lot compared to az aks update --update-cluster-autoscaler
command, is that clear?
Hi @shm007g,
az aks update --update-cluster-autoscaler
command(autoscaler integrated with AKS) is only for AKS and only work with AKS VMSSPreview, it's easier to use; while if you use aks-engine, autoscaler works with both vmss and standard vmtype, but you need to deploy autoscaler by yourself and configure a lot compared toaz aks update --update-cluster-autoscaler
command, is that clear?
I got what you said.
I guess AKS build on aks-engine, AKS can support what aks-engine can support. According what you said, AKS now cut some function of aks-engine?
correct, new features come into aks-engine first, and then AKS adopts those new features later
correct, new features come into aks-engine first, and then AKS adopts those new features later
Thanks.
So, for now cluster-autoscaler is only a preview function even in azure global. A formal cluster-autoscaler for azure china may take a real long time. If we want to use this function in china, i can only use aks-engine/acs-engine instead.
If I get no mistake on upper conclusion, I may close this comment.
By the way, I've build one k8s cluster on acs-engine template with cluster-autoscaler function work well. But boss may want a formal version.
correct, thanks for understanding. AKS will be GA on Azure China in the next few months, and then we will onboard cluster-autoscaler, that's the draft timeline.
correct, thanks for understanding. AKS will be GA on Azure China in the next few months, and then we will onboard cluster-autoscaler, that's the draft timeline.
I got you. Thanks.
Before you begin
part says cluster auto-scale needs at least k8s 1.12.4 and vmss.Operation failed with status: 'Bad Request'. Details: The value of parameter orchestratorProfile.OrchestratorVersion is invalid.
az extension add --name aks-preview
, also failed with status:No registered resource provider found for location 'chinaeast2' and API version '2018-08-01-preview' for type 'managedClusters'. The supported api-versions are '2017-08-31, 2018-03-31'. The supported locations are 'chinaeast2'.