2 votes1 comment · Azure Kubernetes Service (AKS) » Support for Kubernetes features · Flag idea as inappropriate… · Admin →Riccardo commented
For me this problem is related with Global VNET Peering limitation. If I would like to connect to a kubernetes exposed service from a VM running in different VNET connected by Global VNET peering, it fails. I must use VNET2VNET only for this limitation.
Thank you for the suggestion. It would help if you can share your use case.
Please consider using automation approach based on resource manager templates – see https://aka.ms/apimdevops.Riccardo shared this idea ·
50 votesRiccardo commented
This limitation is an headache.
I had to replace my Global VNET peering with VNET2VNET connection (not fair).
I have 2 AKS in 2 different regions and need to connect from one region to the other by ILB.
I cannot use a third party LB, the mission is keep it simple.
Yes please, can you provide an ETA?