Azure
Output VMSS dynamic name within AKS
What happened:
Currently VMSS of AKS is dynamically named and not outputted within AKS.
What you expected to happen:
We are using Infrastructure as Code to provision AKS cluster and enable VM insights for those VMSS. Therefore, we need to read the VMSS name outputted from AKS cluster.
How to reproduce it (as minimally and precisely as possible):
Provision AKS via IaC and no VMSS name in AKS outputs.
Anything else we need to know?: None
Environment:
- Kubernetes version (use
kubectl version): 1.20.9 [AKS version]
Hi minfeihe-tomtom, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.
I might be just a bot, but I'm told my suggestions are normally quite good, as such:
- If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
- Please abide by the AKS repo Guidelines and Code of Conduct.
- If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
- Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
- Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
- If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
Support this, it allow us to spin up App GW whenever AKS is up in a single IaC run.
It can be done easily in AWS ,not sure what stopping AKS from doing that.
I was looking for a way to get (or set) the auto-created VMSS name within an ARM/bicep template in order to add a managed identity to the VMSS for metered billing, but wound up here. So I also request the VMSS name to be accessible (or settable) while deploying the cluster.
Hey all +1 on this would be great to have this feature implemented, especially when vmss is being generated dynamically via the creation of aks clusters, when combined with the option of assigning public IPs to nodes not having this feature it becomes difficult to know what the public IP addresses are programmatically through tools like terraform when the nodes are being created through things like autoscalers so that additional provisioning/hardening of the nodes can take place
Will unsubscribe from this.
I think we can just hope for the best , Azure product roadmap seems to be rigid and not really dev-friendly.
Looks like this still needs attention. I see the bot has been asking for months, has anyone looked at this?
@phealy sicne two of these asks are network related. (app gateway and public ip)
In general though we're tyring to push customers away from touching things inside the node resource group.
