You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using private ip address, you have to specify a vnet and a subnet. Currently, the plugin only support vnet from the same resource group that also the container instance will be used. In some cases, the vnet is set up in a different resource group. Therefore, the name of the resource group should be possible to specify.
This new field could be optional. So the default behaviour is using the same resource group as the container instance will use.
Todo List:
Add new optional field Name of resource group
Extend the documentation
Upstream changes
No response
The text was updated successfully, but these errors were encountered:
What feature do you want to see added?
When using private ip address, you have to specify a vnet and a subnet. Currently, the plugin only support vnet from the same resource group that also the container instance will be used. In some cases, the vnet is set up in a different resource group. Therefore, the name of the resource group should be possible to specify.
This new field could be optional. So the default behaviour is using the same resource group as the container instance will use.
Todo List:
Name of resource group
Upstream changes
No response
The text was updated successfully, but these errors were encountered: