azurerm_kubernetes_cluster - deprecate public_network_access_enabled

[ms-henglu]

I've confirmed with service team, that this feature is not complete and it will not work as expected.

This PR deprecates this field and this field will not pass to the API.

[stephybun]

@ms-henglu the API currently still accepts and returns this field, are there plans to remove this field in a future API version? Does setting it cause unexpected side effects or does it just do nothing?

[katbyte]

can we do a better job of explaining why this is being removed? and link to any public information?

[ms-henglu]

Hi @katbyte , we got confirmation from the service team that this function is not complete yet and they're working on it.

And there's no public doc about this field.

[mybayern1974]

Here is an explanation provided by AKS team suggesting this property is not fully functional ready.

[ms-henglu]

Recently AKS adds a new validation to prevent users creating clusters with "public_network_access_enabled=false" and UDR(user defined routing).

Without this PR, when users create new cluster with UDR, they must change "public_network_access_enabled" to true or remove "public_network_access_enabled=false" from this config. This PR make it easier for users to adopt this validation, users don't need to change their config, and the existing clusters won't be affected.

[stephybun]

Thanks @ms-henglu LGTM 👍

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.