You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 24, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 24, 2026. It is now read-only.
I need my API hosted in AKS to respond in ports 80 and 443. In port 80 because some of my current clients are using port 80 "hardcoded" and their HttpClients do not follow redirects...
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Details
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
You have not provided the information asked in the template of a new bug report. Click the new bug report button and look at the questions asked. Then don't create a new issue but edit this issue description and anwer the questions asked in md format. Once satisfied, then re-open the issue
Generally you will need to create 2 ingresses with different hostnames. One terminated with TLS and the other no tls section.
if you mean to use HTTPS to the backend pod itself then, this controller has a backend-protocol annotation but I don't think you are using this controller.
Also ssl-passthrough does not combine with port 80 obviously
You have not provided the information asked in the template of a new bug report. Click the new bug report button and look at the questions asked. Then don't create a new issue but edit this issue description and anwer the questions asked in md format. Once satisfied, then re-open the issue
Generally you will need to create 2 ingresses with different hostnames. One terminated with TLS and the other no tls section.
if you mean to use HTTPS to the backend pod itself then, this controller has a backend-protocol annotation but I don't think you are using this controller.
Also ssl-passthrough does not combine with port 80 obviously
/close
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Hey there, I was solving this problem for Cozystack, as we were needed to redirect traffic from infra-ingress-controller to user clusters. So, this rule works with no troubles:
Activity
k8s-ci-robot commentedon Apr 30, 2024
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the
triage/acceptedlabel and provide further guidance.The
triage/acceptedlabel can be added by org members by writing/triage acceptedin a comment.Details
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
longwuyuan commentedon Apr 30, 2024
You have not provided the information asked in the template of a new bug report. Click the new bug report button and look at the questions asked. Then don't create a new issue but edit this issue description and anwer the questions asked in md format. Once satisfied, then re-open the issue
Generally you will need to create 2 ingresses with different hostnames. One terminated with TLS and the other no tls section.
if you mean to use HTTPS to the backend pod itself then, this controller has a backend-protocol annotation but I don't think you are using this controller.
Also ssl-passthrough does not combine with port 80 obviously
/close
/close
k8s-ci-robot commentedon Apr 30, 2024
@longwuyuan: Closing this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
ingress forward both 80 and 443 ports to tenant clusters (#235)
kvaps commentedon Jul 26, 2024
Hey there, I was solving this problem for Cozystack, as we were needed to redirect traffic from infra-ingress-controller to user clusters. So, this rule works with no troubles:
longwuyuan commentedon Jul 26, 2024
nginx.ingress.kubernetes.io/secure-backends: 'true'is invalid because it is not-existing in the list here https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/ so config posted is invalid