Skip to content

Commit fa7e10d

Browse files
committed
edits
1 parent a3ec358 commit fa7e10d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/api-management/api-management-kubernetes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ To get a subscription key for accessing APIs, developers need a subscription. A
8787

8888
### Option 3: Deploy API Management inside the cluster virtual network
8989

90-
In some cases, customers that have regulatory constraints or strict security requirements might find Options 1 and 2 nonviable because of the publicly exposed endpoints. In others, the AKS cluster and the applications that consume the microservices might reside within the same virtual network, so there's no reason to expose the cluster publicly because all API traffic remains within the virtual network. In these scenarios, you can deploy API Management into the cluster virtual network. [API Management Developer, Premium, Standard v2, and Premium v2 tiers](https://aka.ms/apimpricing) support virtual network deployment.
90+
In some cases, customers that have regulatory constraints or strict security requirements might find Options 1 and 2 nonviable because of the publicly exposed endpoints. In others, the AKS cluster and the applications that consume the microservices might reside within the same virtual network, so there's no reason to expose the cluster publicly because all API traffic remains within the virtual network. In these scenarios, you can deploy API Management into the cluster virtual network. [API Management Developer, Premium, Standard v2, and Premium v2 (preview) tiers](https://aka.ms/apimpricing) support virtual network deployment.
9191

9292
There are two modes of [deploying API Management into a virtual network](./virtual-network-concepts.md): external and internal.
9393

0 commit comments

Comments
 (0)