Skip to main content
Version: 1.2.0

Install Ingress APISIX on Tencent TKE

This document explains how to install Ingress APISIX on Tencent TKE.


  • Create a TKE Service on Tencent Cloud and make sure the API Server is accessible from your workspace.
  • Install Helm.
  • Download the kube config for your TKE Console.
  • Clone Apache APISIX Charts.
  • Make sure your target namespace exists, kubectl operations thorough this document will be executed in namespace ingress-apisix.

Install APISIX and apisix-ingress-controller#

As the data plane of apisix-ingress-controller, Apache APISIX can be deployed at the same time using Helm chart.

cd /path/to/apisix-helm-chart
helm repo add bitnami
helm repo update
kubectl create ns ingress-apisix
helm install apisix charts/apisix \
--set gateway.type=LoadBalancer \
--set ingress-controller.enabled=true \
--set etcd.persistence.size="10Gi" \
--namespace ingress-apisix
kubectl get service --namespace ingress-apisix

Please be careful you must configure the etcd.persistence.size to multiples of 10Gi (it's a limitation on TKE), otherwise the PersistentVolumeClaim creation will fail.

Five Service resources were created.

  • apisix-gateway, which processes the real traffic;
  • apisix-admin, which acts as the control plane to process all the configuration changes.
  • apisix-ingress-controller, which exposes apisix-ingress-controller's metrics.
  • apisix-etcd and apisix-etcd-headless for etcd service and internal communication.

Two Service resources were created, one is apisix-gateway, which processes the real traffic; another is apisix-admin, which acts as the control plane to process all the configuration changes.

The gateway service type is set to LoadBalancer (see TKE Service Management for more details), so that clients can access Apache APISIX through a load balancer. You can find the load balancer ip by running:

kubectl get service apisix-gateway --namespace ingress-apisix -o jsonpath='{.status.loadBalancer.ingress[].ip}'

Now open your TKE console, choosing your cluster and clicking the Workloads tag, you'll see all pods of Apache APISIX, etcd and apisix-ingress-controller are ready.

Try to create some resources to verify the running status. As a minimalist example, see proxy-the-httpbin-service to learn how to apply resources to drive the apisix-ingress-controller.