support for azurerm_container_group with private ip

[ghost]

This issue was originally opened by @mkyc as hashicorp/terraform#19366. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Use-cases

Allow creation of Azure Container Instances inside vnet described here: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-vnet
this requires possibility to define ipAddress.type: private and networkProfile.id: <profile-id>

[vidarw]

👍 we are also interested in this feature

[metacpp]

@mkyc Thanks for opening this feature request.

We're working on this feature through below steps and we'd like to share the latest progress with you here:

• Upgrade Container Group SDK to 2018-10-01 (Upgrade ACI SDK to 2018-10-01. #2174 )
• Upgrade Network SDK to 2018-08-01 (Upgrade network SDK to 2018-08-01 #2433 )
• Add Delegation in azurerm_subnet. (Add delegation support for Subnet #2042)
• Add Network Profile resource. (New Resource: Azure Network Profile #2636 )
• Update Container Group code to support virtual network.

[pricoppd]

Hi All,

Any update on this please? i'm looking for a way of deploying a container vnet integrated.

[velith]

Updates? This would truly be a useful feature indeed, since it's in some cases blocking to use container groups that exposes them to the public. Thank you!

[pricoppd]

@velith i lost all hope and turn to docker and kube as this one is vnet integrated and supports also windows images.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!