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
Copy file name to clipboardExpand all lines: articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ ms.author: apimpm
18
18
19
19
# Deploy a self-hosted Azure API Management gateway to Azure Kubernetes Service
20
20
21
-
This article provides the steps for deploying self-hosted Azure API Management gateway into an [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/) Cluster. For deploying self-hosted gateway to other Kubernetes clusters (e.g., clusters in a foreign cloud), see [deploy self-hosted gateway to Kubernetes](api-management-howto-deploy-self-hosted-gateway-to-k8s.md).
21
+
This article provides the steps for deploying self-hosted Azure API Management gateway into an [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/)(AKS) Cluster. For deploying self-hosted gateway to other Kubernetes clusters (e.g., clusters in a foreign cloud), see [deploy self-hosted gateway to Kubernetes](api-management-howto-deploy-self-hosted-gateway-to-k8s.md).
22
22
23
23
## Prerequisites
24
24
@@ -41,20 +41,20 @@ This article provides the steps for deploying self-hosted Azure API Management g
41
41
```console
42
42
kubectl apply -f <gateway-name>.yaml
43
43
```
44
-
10. Execute the command. The command instructs your AKS cluster to run the container, using self-hosted gateway's image downloaded from the Microsoft Container Registry, and to configure the container to expose HTTP (8080) and HTTPS (443) ports.
45
-
11. Run the below command to check the gateway pod is running. Note that your pod name will be different.
44
+
11. Execute the command. The command instructs your AKS cluster to run the container, using self-hosted gateway's image downloaded from the Microsoft Container Registry, and to configure the container to expose HTTP (8080) and HTTPS (443) ports.
45
+
12. Run the below command to check the gateway pod is running. Note that your pod name will be different.
0 commit comments