Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

az aks get-credentials should not point to privatelink dns zone

See original GitHub issue

Describe the bug

az aks get-credentials generate an entry on ~/.kube/config pointing to privatelink via private zone. Example:

https://my-aks-cluster-my-aks-cluster-a12345-a1234567.privatelink.<region>.azmk8s.io:443
name: my-aks-cluster

The correct address should be:

https://my-aks-cluster-my-aks-cluster-a12345-a1234567.hcp.<region>azmk8s.io

If I’m understanding this wrongly, maybe the documentation on https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-dns#on-premises-workloads-using-a-dns-forwarder should be updated.

Environment Summary

macOS-11.6.3-x86_64-i386-64bit, Darwin 20.6.0
Python 3.10.2
Installer: HOMEBREW

azure-cli 2.32.0 *

Extensions:
azure-devops 0.23.0
ssh 1.0.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

weltonrodrigocommented, Mar 23, 2022

—public-fqdn gives me the public zone. Thank you.

Em 22 de mar. de 2022, à(s) 21:59, SaurabhSharma-MSFT @.***> escreveu:

@weltonrodrigo https://github.com/weltonrodrigo Can you please try using az aks get-credentials -n <cluster> -g <rg> --public-fqdn ?

— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-cli/issues/21584#issuecomment-1075799164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMRQZE7BCR753LHRFK3NU3VBJUH3ANCNFSM5QNDTBHQ. You are receiving this because you were mentioned.

0reactions

SaurabhSharma-MSFTcommented, Mar 23, 2022

@weltonrodrigo No problem. Thanks. We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.