I'd love to set up HSTS with my GKE cluster, as right now HTTP requests return a Google broken robot 404 page after setting this up in ingress.yml annotations: kubernetes.io/ingress.allow-http: "false"

Apparently there are options for this in ingress.yml (namely hsts-max-age and hsts-include-subdomains), but as far as I understand it's not supported by GKE: https://github.com/kubernetes/ingress/blob/7c749ede0a2d88f289279d61d04005e22f002104/docs/annotations.md#tls-related

I'd really like to avoid using and maintaining a custom Nginx load balancer and losing Google's scaling, sticking to the default one would be a strong requirement. I'd also like to avoid letting HTTP requests pass through and handling redirects and the HSTS header in my app.

If HSTS isn't possible, I could live with a good redirection setup.

Thanks a lot!


HSTS is currently not possible by Google Cloud Load Balancer. There is a feature request already open for this feature . You can subscribe to the feature request for updates.

  • Thanks a lot for the response, I starred the issue. Is there any way with the load balancer to handle HTTP -> HTTPS redirection, or my only option is doing it in my application (or using a custom load balancer)? – dain Jul 20 '17 at 8:33
  • The redirection is not yet supported directly from the load balancer, however, this issue report has recommendations how to do that in your app. – Faizan Jul 20 '17 at 15:40
  • Thanks, so it seems right now the only option is to do the redirection in the backend application layer using the X-Forwarded-Proto http header set by the load balancer: serverfault.com/questions/733166/… – dain Jul 21 '17 at 10:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.