Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import-AzAksCredential is missing the Public-FQDN functionality #17711

Closed
fschmied opened this issue Apr 4, 2022 · 1 comment · Fixed by #19226
Closed

Import-AzAksCredential is missing the Public-FQDN functionality #17711

fschmied opened this issue Apr 4, 2022 · 1 comment · Fixed by #19226
Labels
AKS customer-reported feature-request This issue requires a new behavior in the product in order be resolved.

Comments

@fschmied
Copy link

fschmied commented Apr 4, 2022

Description of the new feature

With a private cluster, AKS will create two DNS entries: a private one and a public one. Import-AzAksCredential imports a kubeconfig with the private DNS name.

Sometimes, you need the public DNS name, e.g., when the machine you're connecting from can't resolve the private one. Azure CLI's az aks get-credentials therefore has a --public-fqdn option.

Import-AzAksCredential is missing that option and should get it, too.

Proposed implementation details (optional)

Should work the same way as az aks get-credentials --public-fqdn.

@fschmied fschmied added feature-request This issue requires a new behavior in the product in order be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Apr 4, 2022
@ghost ghost added customer-reported and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Apr 4, 2022
@dingmeng-xue
Copy link
Member

Thanks for reporting. We will look into it.

@wyunchi-ms wyunchi-ms linked a pull request Aug 16, 2022 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AKS customer-reported feature-request This issue requires a new behavior in the product in order be resolved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants