Allow k8s nodes/agent pool to be created in different/multiple availability zones, to support a highly-available (HA) cluster130 votes
We use Azure Policy to ensure all our resources inherit tags from their resource group. Cost Center being the big one for our company.
This policy fails when AKS creates an additional resource group, and has been requiring us to manually intervene and apply the cost center tag.
In the absence of removing that resource group altogether, it would be great if in the interim, the MC_ Resource Group could have the option to inherit the tags from the AKS resource in the original resource group.2 votes
Looking for an option to choose Kubernetes Load Balancer as SKU Standard rather than SKU Basic either while creating cluster or post creation. Either way fine.
Limiting not to rollout large scale clusters2 votes
- Don't see your idea?