Kubernetes NGINX Ingress Controller未获取TLS证书

job*_*ers 9 ssl nginx kubernetes google-kubernetes-engine

我使用nginx-ingress控制器在GKE上设置了一个新的kubernetes集群.TLS不起作用,它使用假证书.

有很多配置细节,所以我做了一个回购 - https://github.com/jobevers/test_ssl_ingress

简而言之,步骤是

  • 创建一个没有GKE负载均衡器的新集群
  • 用我的密钥和证书创建一个秘密
  • 创建一个nginx-ingress部署/ pod
  • 创建一个入口控制器

nginx-ingress配置来自https://zihao.me/post/cheap-out-google-container-engine-load-balancer/(看起来非常类似于ingress-nginx repo中的很多示例).

我的ingress.yaml与示例几乎完全相同

当我跑弯时,我明白了

$ curl -kv https://35.196.134.52
[...]
*    common name: Kubernetes Ingress Controller Fake Certificate (does not match '35.196.134.52')
[...]
*    issuer: O=Acme Co,CN=Kubernetes Ingress Controller Fake Certificate
[...]
Run Code Online (Sandbox Code Playgroud)

这表明我仍在使用默认证书.

我该如何使用我的?


入口定义

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ssl-ingress
  annotations:
    kubernetes.io/ingress.class: "nginx"
spec:
  tls:
    - secretName: tls-secret
  rules:
  - http:
      paths:
      - path: /
        backend:
          serviceName: demo-echo-service
          servicePort: 80
Run Code Online (Sandbox Code Playgroud)

创造秘密:

kubectl create secret tls tls-secret --key tls/privkey.pem --cert tls/fullchain.pem
Run Code Online (Sandbox Code Playgroud)

进一步调试,证书正在服务器上找到并存在:

$ kubectl -n kube-system exec -it $(kubectl -n kube-system get pods | grep ingress | head -1 | cut -f 1 -d " ") -- ls -1 /ingress-controller/ssl/
default-fake-certificate-full-chain.pem
default-fake-certificate.pem
default-tls-secret-full-chain.pem
default-tls-secret.pem
Run Code Online (Sandbox Code Playgroud)

而且,从日志中,我看到了

kubectl -n kube-system log -f $(kubectl -n kube-system get pods | grep ingress | head -1 | cut -f 1 -d " ")
[...]
I1013 17:21:45.423998       6 queue.go:111] syncing default/test-ssl-ingress
I1013 17:21:45.424009       6 backend_ssl.go:40] starting syncing of secret default/tls-secret
I1013 17:21:45.424135       6 ssl.go:60] Creating temp file /ingress-controller/ssl/default-tls-secret.pem236555242 for Keypair: default-tls-secret.pem
I1013 17:21:45.424946       6 ssl.go:118] parsing ssl certificate extensions
I1013 17:21:45.743635       6 backend_ssl.go:102] found 'tls.crt' and 'tls.key', configuring default/tls-secret as a TLS Secret (CN: [...])
[...]
Run Code Online (Sandbox Code Playgroud)

但是,看看nginx.conf,它仍然使用假证书:

$ kubectl -n kube-system exec -it $(kubectl -n kube-system get pods | grep ingress | head -1 | cut -f 1 -d " ") -- cat /etc/nginx/nginx.conf | grep ssl_cert
        ssl_certificate                         /ingress-controller/ssl/default-fake-certificate.pem;
        ssl_certificate_key                     /ingress-controller/ssl/default-fake-certificate.pem;
Run Code Online (Sandbox Code Playgroud)

job*_*ers 11

事实证明,入口定义需要如下所示:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ssl-ingress
  annotations:
    kubernetes.io/ingress.class: "nginx"
spec:
  tls:
    - hosts:
      - app.example.com
      secretName: tls-secret
  rules:
    - host: app.example.com
      http:
        paths:
        - path: /
          backend:
            serviceName: demo-echo-service
            servicePort: 80
Run Code Online (Sandbox Code Playgroud)

规则下的主机条目需要与tls下的一个主机条目匹配.

  • 此配置应如何查找通配符证书和域? (2认同)