-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
field ingress.spec.defaultBackend.service.port.number is broken #11517
Comments
/triage accepted Unfortunately, what is know is that the field Because the flag There is some info in that other issue that the problem was caused by this PR #8825 . I will create a issue to explore reverting what that PR changed @Gacko any comments @rikatz @strongjz @tao12345666333 if it is as simple as reverting #8825, would you want to review/consider it |
@harry1064 any comments |
/retitle field ingress.spec.defaultBackend.service.port.number is broken |
This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach |
i can't reproduce this in kind, this is my yaml:
|
What happened:
I've set up Minikube with nginx ingress and ssl-passthrough. When I specify in the ingress the port name it works, but it doesn't work when specifying the port number.
What you expected to happen:
I expected specifying a port number in the Ingress would work as well.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Kubernetes version (use
kubectl version
):Environment: minikube version: v1.33.1
How to reproduce this issue:
Ingress that doesn't work (note that "port.number" is set)
Ingress that works (note that "port.name" is set):
Service
Configuration logged by Nginx.
You'll see that in one of the configs the PassthroughBackends has set port 0 when it is broken, and a port 8443 when it works.
The text was updated successfully, but these errors were encountered: