Migrating from Azure CNI V1 to CNI Overlay is now possible without replacement

[damienpontifex]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

Release 2023-06-11 of AKS now notes "Migrating a cluster from Azure CNI V1 to CNI Overlay is GA now."

The kubernetes_cluster_resource explicitly marks this as ForceNew

terraform-provider-azurerm/internal/services/containers/kubernetes_cluster_resource.go

Line 1044 in c21a632

ForceNew: true,

New or Affected Resource(s)/Data Source(s)

kubernetes_cluster_resource

Potential Terraform Configuration

No change from user code, only change within provider

References

• https://github.com/Azure/AKS/releases/tag/2023-06-11
• https://learn.microsoft.com/en-us/azure/aks/azure-cni-overlay#upgrade-an-existing-cluster-to-cni-overlay

[aristosvo]

I'll take a look!

[github-actions]

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