-
Notifications
You must be signed in to change notification settings - Fork 583
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
nginx-ingress-controller does not bind to required ingress ports even after specifying http-port and https-port in RKE cluster config #1876
Comments
Hi, just adding a note, also please see rancher/rancher#17857. These options in RKE cluster config, configures
|
I believe the documentation does mention that ingress controller is bound to port 80 and 443 only. Template code indicating the ingress ports are bound to 80/443: Host networking enabled on the daemonset. |
@ibrokethecloud thanks for this, yes if you're referring to this documentation https://rancher.com/docs/rke/latest/en/config-options/add-ons/ingress-controllers/ Then you're right it does mention that it is bound to |
Linking related PR rancher/kontainer-driver-metadata#109 |
I've run into the same thing... followed the post from @meappy and got everything moved to 8080 and 8443 as well. However, one of the things I've noticed now is that in the Workloads screen in the Rancher interface it still shows things deployed on port 80 and when you click the links they still go to port 80... which is obviously dead now. If you change the port to 8080, it works fine. Also, |
Available to test in RKE |
Also tested in:
|
RKE version:
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Azure VM
cluster.yml file:
Steps to Reproduce:
nginx-ingress-controller
to listen on portsHTTP/8080
andHTTPS/8443
cluster.yml
filenginx-ingress-controller
continues to be bound toHostPort
80
and443
Results:
nginx-ingress-controller
daemonset resource like so:kubectl delete pod -l app=ingress-nginx -n ingress-nginx
to get fresh pods deployed with the modified configHostPort
8080
and8443
HostPort
HTTP/8080
andHTTPS/78443
The text was updated successfully, but these errors were encountered: