Skip to content

Commit 309ee75

Browse files
Merge pull request #218963 from prasha-microsoft/patch-9
Update chaos-studio-private-networking.md
2 parents 9e08875 + 1fb890f commit 309ee75

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/chaos-studio/chaos-studio-private-networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ VNet injection allows Chaos resource provider to inject containerized workloads
6666
5. Start the experiment.
6767
6868
## Limitations
69-
* At present the VNet injection will only be possible in subscriptions/regions where Azure Container Instances and Azure Relay are available.
69+
* At present the VNet injection will only be possible in subscriptions/regions where Azure Container Instances and Azure Relay are available. They are deployed to target regions.
7070
* When you create a Target resource that you would like to enable with VNet injection, you will need Microsoft.Network/virtualNetworks/subnets/write access to the virtual network. For example, if the AKS cluster is deployed to VNet_A, then you must have permissions to create subnets in VNet_A in order to enable VNet injection for the AKS cluster. You will have to specify a subnet (in VNet_A) that the container will be deployed to.
7171
7272
Request Body when created Target resource with VNet injection enabled:

0 commit comments

Comments
 (0)