kubernetes - Two resource groups created for an ACS cluster -


i don't understand why separate resource group created of infrastructure associated acs cluster, , not resource group specify when creating cluster? leave defined resource group 1 lonely entity (the acs cluster definition) , whole new resource group name don't control. not fan of this.

i using azure cli create acs cluster, i'm "guessing" if went arm route i'd have more control. still, limitation reside , why?

here's cli command:

az acs create -n=int-madraskube -g=internal-acs --orchestrator-type=kubernetes  --agent-count=2 --generate-ssh-keys --windows --admin-username={myadmin} --admin-password={mypassword} --service-principal={sp_guid} --client-secret={secret_guid} 

and end 2 resource groups:

internal-acs

internal-acs_int-madraskube_westus2

this new design of acs (v2) in selected regions. in past (the v1), created resources in same resource group container service resource is. makes hard clean resources when delete container service resource. being in new resource group (preferably locked down , invisible, not possible right now), it's 1 step closer managed service.

for more info acs v2, https://github.com/azure/acs


Comments

Popular posts from this blog

ZeroMQ on Windows, with Qt Creator -

unity3d - Unity SceneManager.LoadScene quits application -

python - Error while using APScheduler: 'NoneType' object has no attribute 'now' -