-
Notifications
You must be signed in to change notification settings - Fork 2.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
Ingress not working outside of host on cluster upgrade #7586
Comments
Couple of additional notes:
|
I'm curious if reverting #7210 fixes this. |
Could it be related to #7561 |
Unlike rules managed by the kubelet/kube-router/flannel, CNI plugin rules are only created when the pod starts. If we remove them in the install script, networking to existing pods (such portmap rules for nodePort pods) will be broken until the pods are deleted and recreated. We should not clean CNI rules in the install script. Root cause on this is the install script change in #7274 |
This is working following the same steps and upgrading to the same versions. This is also working with system-upgrade-controller upgrades (as a regression test). |
Environmental Info:
K3s Version: Upgraded from
v1.25.9+k3s1
tov1.26.4+k3s1
Node(s) CPU architecture, OS, and Version:
Cluster Configuration: 1 node
Describe the bug:
Steps To Reproduce:
config.yaml
Steps:
curl -sfL https://get.k3s.io/ | INSTALL_K3S_VERSION=v1.25.9+k3s1 sh -
kubectl apply -f ing.yaml
(Attached ing.yaml below)curl -H 'Host: [test2.com](http://test2.com/)' http://xx.xxx.xx.xxx/name.html
. Expected result likeingresstest-deploy-abcde
curl -sfL https://get.k3s.io/ | INSTALL_K3S_VERSION=v1.26.4+k3s1 sh -
Failed to connect: port 80 after 46 ms: Couldn't connect to server
Expected behavior:
curl ingress should continue to work outside of host after upgrade
Actual behavior:
curl fails with
Failed to connect xx.xx.xx.xx port 80 after 46 ms: Couldn't connect to server
Additional context / logs:
logs.zip
The text was updated successfully, but these errors were encountered: