You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To be able to disable the public FQDN of the Kubernetes apiserver.
Actual Behavior
Public FQDN is present and can not be disable.
Versions used
Pulumi 3.29.1
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
The default top level resources correspond to v2021-03-01 of the api spec published by azure. Due to the large api version splay in azure api specifications our docs currently only provide the latest "stable" api version (and not previews).
It is also available in version V20220701 of this SDK, which does not appear to be a preview. We are using Golang and unfortunately it is not available there using the default version.
What happened?
In Azure AKS it is possible to disable the public FQDN of the API server using the enablePrivateClusterPublicFQDN property, see the official documentation:
https://docs.microsoft.com/de-de/azure/templates/microsoft.containerservice/managedclusters?tabs=json#managedclusterapiserveraccessprofile
The Azure-native Pulumi SDK seems to be missing the option to configure this.
The older SDK was containing this property:
https://www.pulumi.com/registry/packages/azure/api-docs/containerservice/kubernetescluster/#state_privateclusterpublicfqdnenabled_go
Please, adjust the azure-native SDK to be able to disable the public FQDN.
Steps to reproduce
Expected Behavior
To be able to disable the public FQDN of the Kubernetes apiserver.
Actual Behavior
Public FQDN is present and can not be disable.
Versions used
Pulumi 3.29.1
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: