Container Service: Add version 2025-03-01

[hqhqhqhqhqhqhqhqhqhqhq]

Tested by generating the sdk locally & passed.

[jackofallops]

Note to the reviewer:
This API contains a breaking behavioural change to LROs that needs to be investigated for the AzureRM Provider before it can be used. Specifically, free-form statuses for status and provisioningState can be used which will break the current "known-state" expectations of the poller.

[hqhqhqhqhqhqhqhqhqhqhq]

Hi @jackofallops can this be merged so other resources under container service can add support for new properties in this api version, e.g. the fleets resource is adding a new feature to auto upgrade & only availble in this API.

I have checked with the service team that this API version will only impact AKS resource -> would it be better to have this version merged & I will a comment in the provider repo telling people not to use this version for AKS only

[thpham]

Hello,

I'm waiting as well for this to be merged so we can start re-introducing previous v3 features, like those documented here. At least as far I was able to understand the workflow... let me know if I could help for something ! thank you.

[jeffhuenemann]

@jackofallops Any thoughts on @hqhqhqhqhqhqhqhqhqhqhq 's comment above? This is a main blocker of important features (such as AKS VNet integrated control plane) getting into v4.x of the azurerm terraform provider. While we're stuck on v3.x, we're starting to get pretty timeboxed - for example, support for Azure Managed Grafana v10 ends next month, but v11 isn't supported until azurerm v4.x.

[jackofallops]

will be unblocked by hashicorp/go-azure-sdk#1221

[jackofallops]

Thanks @hqhqhqhqhqhqhqhqhqhqhq
Can you take a look at removing the versions that are no longer in use by the Azure RM provider here, we should be mindful of the number of versions we include and not simply add indefinitely.

[jackofallops]

Can we remove the versions no longer referenced by the provider?

[hqhqhqhqhqhqhqhqhqhqhq]

I have removed some of the old & not used versions of ContainerService

[Chippiewill]

Is there a reason for not adding 2025-05-01 (latest stable) instead? That version is required for node auto-provisioning.

[weisdd]

I agree with @Chippiewill, let's add 2025-05-01 as well, it'll unblock hashicorp/terraform-provider-azurerm#30190

[jackofallops]

@hqhqhqhqhqhqhqhqhqhqhq - Given the feedback, is it worth skipping 2025-03-01 and jumping straight to 2025-05-01?