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
This article provides the steps for deploying self-hosted gateway component of Azure API Management to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/). For deploying self-hosted gateway to a Kubernetes cluster, see the how-to article for deployment by using a [deployment YAML file](how-to-deploy-self-hosted-gateway-kubernetes.md) or [with Helm](how-to-deploy-self-hosted-gateway-kubernetes-helm.md).
15
+
This article provides the steps for deploying self-hosted gateway component of Azure API Management to [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/services/kubernetes-service/). For deploying self-hosted gateway to a Kubernetes cluster, see the how-to article for deployment by using a [deployment YAML file](how-to-deploy-self-hosted-gateway-kubernetes.md) or with [Helm](how-to-deploy-self-hosted-gateway-kubernetes-helm.md).
16
16
17
17
> [!NOTE]
18
18
> You can also deploy self-hosted gateway to an [Azure Arc-enabled Kubernetes cluster](how-to-deploy-self-hosted-gateway-azure-arc.md) as a [cluster extension](/azure/azure-arc/kubernetes/extensions).
@@ -26,16 +26,16 @@ This article provides the steps for deploying self-hosted gateway component of A
26
26
## Deploy the self-hosted gateway to AKS
27
27
28
28
1. Select **Gateways** from under **Deployment and infrastructure**.
29
-
2. Select the self-hosted gateway resource you intend to deploy.
30
-
3. Select **Deployment**.
31
-
4. A new token in the **Token** text box was autogenerated for you using the default **Expiry** and **Secret Key** values. Adjust either or both if desired and select **Generate** to create a new token.
32
-
5. Make sure **Kubernetes** is selected under **Deployment scripts**.
33
-
6. Select **\<gateway-name\>.yml** file link next to **Deployment** to download the file.
34
-
7. Adjust the `config.service.endpoint`, port mappings, and container name in the .yml file as needed.
35
-
8. Depending on your scenario, you might need to change the [service type](/azure/aks/concepts-network-services).
36
-
* The default value is `LoadBalancer`, which is the external load balancer.
37
-
* You can use the [internal load balancer](/azure/aks/internal-lb) to restrict the access to the self-hosted gateway to only internal users.
38
-
* The sample below uses `NodePort`.
29
+
1. Select the self-hosted gateway resource you intend to deploy.
30
+
1. Select **Deployment**.
31
+
1. A new token in the **Token** text box was autogenerated for you using the default **Expiry** and **Secret Key** values. Adjust either or both if desired and select **Generate** to create a new token.
32
+
1. Make sure **Kubernetes** is selected under **Deployment scripts**.
33
+
1. Select the**\<gateway-name\>.yml** file link next to **Deployment** to download the file.
34
+
1. Adjust the `config.service.endpoint`, port mappings, and container name in the .yml file as needed.
35
+
1. Depending on your scenario, you might need to change the [service type](/azure/aks/concepts-network-services).
36
+
- The default value is `LoadBalancer`, which is the external load balancer.
37
+
- You can use the [internal load balancer](/azure/aks/internal-lb) to restrict the access to the self-hosted gateway to only internal users.
38
+
- The following sample uses `NodePort`.
39
39
1. Select the **copy** icon located at the right end of the **Deploy** text box to save the `kubectl` command to clipboard.
40
40
1. Paste the command to the terminal (or command) window. The command expects the downloaded environment file to be present in the current directory.
41
41
@@ -44,31 +44,33 @@ This article provides the steps for deploying self-hosted gateway component of A
44
44
```
45
45
46
46
1. Execute the command. The command instructs your AKS cluster to:
47
-
* Run the container, using self-hosted gateway's image downloaded from the Microsoft Container Registry.
48
-
* Configure the container to expose HTTP (8080) and HTTPS (443) ports.
49
-
1. Run the below command to check the gateway pod is running. Your pod name will be different.
47
+
- Run the container, using self-hosted gateway's image downloaded from the Microsoft Container Registry.
48
+
- Configure the container to expose HTTP (8080) and HTTPS (443) ports.
49
+
1. Run the following command to check that your gateway pod is running. This pod name is an example.
0 commit comments