title: Kubernetes ingress on GKE results in 502 response on http / SSL_ERROR_SYSCALL on https
body: <p>I've tested my configuration on minikube where it works perfectly, however on GKE I run into an error of HTTP responding with 502 while the HTTPS gets the connection terminated?</p>
  
  <p>I have no idea how to diagnose this issue, which logs could I look at? </p>
  
  <p>Here is a verbose curl log when accessing over https://</p>
  
  <pre><code>* Expire in 0 ms for 1 (transfer 0x1deb470)
  * Expire in 0 ms for 1 (transfer 0x1deb470)
  * Expire in 0 ms for 1 (transfer 0x1deb470)
  *   Trying 35.244.154.110...
  * TCP_NODELAY set
  * Expire in 200 ms for 4 (transfer 0x1deb470)
  * Connected to chrischrisexample.de (35.244.154.110) port 443 (#0)
  * ALPN, offering h2
  * ALPN, offering http/1.1
  * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
  * TLSv1.2 (OUT), TLS header, Certificate Status (22):
  * TLSv1.2 (OUT), TLS handshake, Client hello (1):
  * OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to chrischrisexample.de:443 
  * Closing connection 0
  curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to chrischrisexample.de:443 
  </code></pre>