https://rancher.com/ logo
Title
c

chilly-iron-96675

06/13/2022, 7:32 PM
Has anyone encountered ingress unavailable after an RKE upgrade? I've just upgraded a 3-node test cluster from
v1.3.2
to
v1.3.11
and afterwards I found that I couldn't connect to the ingress anymore.
ingress:
    provider: nginx
    network_mode: hostPort
    http_port: 80
    https_port: 443
The pods are running, I've explicitly set the ports in the cluster.yml but nginx doesn't seem to be answering TCP requests on either 80 or 443. Has anyone else experienced ingress unavailable after an
rke up
?
Interestingly enough bouncing the hosts corrected the issue... Almost like nginx didn't let go of the port after it was replaced during the upgrade...
n

nice-waiter-47552

06/13/2022, 11:53 PM
I had this on ALL of my hosts in two clusters just recently updated from 1.20 through to 1.23 (one ver at a time). All but one of the hosts was not passing traffic to the ingress.
Had to cordon drain and reboot each one in turn to recover services.