-
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
Kube Proxy cannot route traffic to pods running on different nodes (Fedora IoT 31) #2069
Comments
Also tested this with libvirt. It runs into the same problem. So, removing the HyperV VM from the title |
Using the ingress to route traffic to different hosts works! apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: kubernetes-bootcamp
spec:
rules:
- host: kubernetes-bootcamp.192.168.122.102.xip.io
http:
paths:
- path: /
backend:
serviceName: kubernetes-bootcamp
servicePort: 8080 kubectl apply -f my-ingress.yaml [root@first ~]# curl kubernetes-bootcamp.192.168.122.102.xip.io
Hello Kubernetes bootcamp! | Running on: kubernetes-bootcamp-6f6656d949-csxzp | v=1
[root@first ~]# curl kubernetes-bootcamp.192.168.122.102.xip.io
Hello Kubernetes bootcamp! | Running on: kubernetes-bootcamp-6f6656d949-dph7z | v=1
[root@first ~]# curl kubernetes-bootcamp.192.168.122.102.xip.io
Hello Kubernetes bootcamp! | Running on: kubernetes-bootcamp-6f6656d949-p4nrb | v=1
[root@first ~]# curl kubernetes-bootcamp.192.168.122.102.xip.io
Hello Kubernetes bootcamp! | Running on: kubernetes-bootcamp-6f6656d949-qj97v | v=1
[root@first ~]# curl kubernetes-bootcamp.192.168.122.102.xip.io
Hello Kubernetes bootcamp! | Running on: kubernetes-bootcamp-6f6656d949-csxzp | v=1 Also works from a different VM in the same virtual network that does not belongs to the cluster |
I'm seeing the same with fedora-iot 33 on Raspberry PI 4s. If I run this daemonset:
And then run this script:
Pods on the same node (so 2 <-> 2, 3<->3) can communicate but not on different nodes, when deploying with vxlan. If I set to host-gw, all pods can communicate. In my cluster, I've set selinux=disabled, and disabled firewalld. This is a new cluster with fresh installs of Fedora-IOT 33 and k3s v1.20.5+k3s1. |
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions. |
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
[root@second test]# uname -a Linux second.mshome.net 5.5.17-200.fc31.x86_64 rancher/k3s#1 SMP Mon Apr 13 15:29:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
2 VMs running Fedora IoT 31
1 VM (first.mshome.net) is the primary
1 VM (second.mshome.net) is the secondary
HOST GW mode used instead of default VXLAN because of #2049
Describe the bug:
Running the Kubernetes Basic sample to test my deployment.
The hosts were deployed following the Kubernetes on Fedora IoT with k3s post
The primary is deployed with:
The secondary is deployed with:
After everything is started, nodes are up and running
Deployment of the test pods is successful:
Trying to communicate with the pods trough the Kube Proxy fails for pods not in the same host
Deploying a service, and using Kube Proxy to communicate with the service also fails when it tries to route to pods in different nodes:
Additionally, using the service deployed in the node directly yields the same issue:
Steps To Reproduce:
Included above
Expected behavior:
All the pods should be addressable using the Kube Proxy
Actual behavior:
Only pods in the same node are addressable using the Kube Proxy
Additional context / logs:
The text was updated successfully, but these errors were encountered: