Enable ingress nginx in TKE | 为腾讯的K8S集群启用nginx ingress

腾讯云集群默认不提供nginx类型的ignress，而默认的实现并不能很好的支持多ingress的泛域名解析场景, 因为每个ingress都会有独立的公网IP。

Nginx is not the default ingress class in TKE. The default implementation doesn't support wildcard domain well, cause each ingress would have it's own public ip address.

幸运的是nginx的ingress实现也是被腾讯云TKE支持的。

The nginx ingress is supported by TKE as well.

我们采用helm的方式来安装。

We use helm to install the implementation.

确保helm已经安装到集群 | Make sure the helm is installed (we use aliyun mirror in China)

helm init --upgrade --force-upgrade \
-i registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.12.2

clone helm-charts

git clone --depth=1 https://github.com/helm/charts.git

安装 | Install

cd charts
helm install --name gocloudio-nginx-ingress \
--namespace gocloudio-nginx-ingress \
./stable/nginx-ingress \
--set-string controller.image.repository=quay-mirror.qiniu.com/kubernetes-ingress-controller/nginx-ingress-controller \
--set-string controller.ingressClass=gocloudio-nginx \
--set controller.replicaCount=4

gocloudio-nginx是ingress class的类型，需要在声明ingress的时候指定, controller.replicaCount可以按需调整

gocloudio-nginx is the name of the custom ingress class. It's the value which is used when a new ingress is declared. The value of controller.replicaCount can be adjusted

这里我们使用了七牛的quay.io的mirror，解决quay.io在国内被屏蔽的问题

配置示例 | Example

可以通过命令 kubectl --namespace gocloudio-nginx-ingress get services -o wide 获取nginx ingress的公网IP，用该ip地址添加到ingress配置里host的A记录里就能实现访问

ingress的.metadata.annotations里必须声明 kubernetes.io/ingress.class 它的值和安装时指定的ingress class一致

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: gocloudio-nginx
    nginx.ingress.kubernetes.io/proxy-body-size: 100m
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "300"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "300"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "300"
  name: pe-main
spec:
  rules:
  - host: portal.gocloudio.com
    http:
      paths:
      - backend:
          serviceName: portal
          servicePort: 80
        path: /
status:
 loadBalancer: {}

Update (2020-01-15)

在使用 [helm3] 的情况下，不必再安装tiller.

Tiller is not required anymore for [helm3].

A bite of code