Closed bakayolo closed 6 years ago
@bappr you're using a container image of a different NGINX Ingress controller. That Ingress controller supports the feature in question differently. Please see https://github.com/kubernetes/ingress-nginx for more info.
The container image of the Ingress controller from this repo is available at https://hub.docker.com/r/nginx/nginx-ingress/ See this doc to find out about the key differences between NGINX Ingress controller implementations
Arf. Thanks for the reply. Indeed, I should have been more careful when choosing the k8s image. Will switch to the other one right now. Thanks a lot.
Describe the bug
ssl-services
does not enableproxy_pass https://...
in the nginx conf.To Reproduce Steps to reproduce the behavior:
https://test.kintohub.com
-> Error 400 Bad Request/etc/nginx/nginx.conf
and I can see that the proxy_pass is set tohttp
, not tohttps
. Switching manually fromhttp
tohttps
and reloading the nginx conf works.Expected behavior Annotation
nginx.org/ssl-services: "test"
should update my nginx conf and replaceproxy_pass http://test.kintohub.com
withproxy_pass https://test.kintohub.com
Your environment
gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.15