Support for Service Fabric Managed Cluster Subnet ID (BYO vNET)

[musaugurlu]

Is there an existing issue for this?

• [X] I have searched the existing issues

Community Note

• Please vote on this issue by adding a :thumbsup: 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

Description

Microsoft has brought bring your own vnet (byovnet) feature to Service Fabric Managed Cluster in the API version 2022-01-01. With this feature, you can set your own subnet id to the managed cluster. Microsoft's rest API reference documentation shows 2018-02-01 API version as the latest API version, but Service Fabric's own documentation shows the 2022-01-01 API version as the latest. Azure's resource explorer shows the subnetId option, too (https://resources.azure.com/subscriptions/\<subscription id>/resourceGroups/\<rg name>/providers/Microsoft.ServiceFabric/managedClusters/\<cluster name>).

I was wondering if we can have a subnetid option in the azurerm_service_fabric_managed_cluster resource.

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

azurerm_service_fabric_managed_cluster

Potential Terraform Configuration

resource "azurerm_service_fabric_managed_cluster" "example" {
...
subnetId = /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/my-sweet-rg/providers/Microsoft.Network/virtualNetworks/my-sweet-vnet/subnets/my-sweet-subnet
...
}

References

https://docs.microsoft.com/en-us/azure/templates/microsoft.servicefabric/2022-01-01/managedclusters

[josefernandezatceiba]

+1

[pbaumgartner-rdt]

+1