https without ssl #2895
Unanswered
mehmetcolgecen
asked this question in
Q&A
Replies: 1 comment 3 replies
-
If the Ingress Controller is not performing SSL termination, and you have SSL traffic - the Ingress Controller is performing SSL pass-through for the SSL traffic. That sounds like:
You will need to use TransportServer for both port 80 and 443 then, assuming they are the same hostname. Assuming I am correctly understanding what you are trying to accomplish. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am working with both http and https ports on different apps. if I use this approach I suppose all ingresses is going to redirected to 443 port. But I need to use both 80 and 443 ports on different hosts without any TLS configuration.
I think "ingress.kubernetes.io/ssl-redirect" annotation should work for this purpose but when I use it I cant track any redirection on conf file. But it should provide redirection according to:
If I use "nginx.org/redirect-to-https" I can track redirection on the conf but it is based on http_x_forwarded_proto and it requires SSL termination but I dont use TLS.
I can see following snippet on /etc/nging/conf.d/xxx.conf when I use nginx.org/redirect-to-https this annotation and If I am not wrong this is not my solution.
But I don't se any snippet on /etc/nging/conf.d/xxx.conf when I use ingress.kubernetes.io/ssl-redirect. I think I should see some snippet something like below which may be a solution of my problem.
return 301 https://$host$request_uri;
Is there any workaround for my situation or should I wait for the update?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions