卷曲到托管在kuberetes上的应用程序返回502 Bad Gateway

Question

curl -v -k https://xxxx.yyyy.zzzz.pp/
*   Trying 143.204.181.115...
* Connected to xxxx.domain.name.something (143.204.181.115) port 443 (#0)
* SSL peer handshake failed, the server most likely requires a client certificate to connect
* Closing connection 0
curl: (35) SSL peer handshake failed, the server most likely requires a client certificate to connect

Answer 1

这与入口控制器设置有关，后者是对应用程序入口的请求进行负载平衡。如果入口的注释规范的格式不正确（即

），则会出现问题

    nginx.ingress.kubernetes.io/secure-backends - if the nginx ingress controller is setup using the chart https://github.com/kubernetes/ingress-nginx

    ingress.kubernetes.io/secure-backends - if the nginx ingress controller is setup using the KOPS https://github.com/kubernetes/kops/tree/master/addons/ingress-nginx

“ nginx”。必须删除注释中的所有内容，这可以解决遇到应用程序URL时出现的502 Bad Gateway错误。