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
UDP broadcast fails between pods #1063
Comments
will try to take a look at this tomorrow but also |
@BenTheElder: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
does UDP broadcast work for a normal Kubernetes cluster? |
Running this same test:
Also does not work on a newly created GKE cluster with standard options. |
the pods in fact schedule on different nodes. I don't think it's expected in Kubernetes's network model that you can broadcast between pods like this. |
You could try using I remembered there was a slack-thread in #kind related to this issue and looked back:
Right, so this could probably be done with https://kubernetes.io/docs/concepts/services-networking/service/ is probably the right starting point for this. |
I'm going to close this out as not a bug in kind, but you may find more help in #kubernetes-users or maybe #sig-networking in the Kubernetes slack with the general problem of service discovery in Kubernetes. |
What happened:
After starting a kind cluster and creating two StatefulSet pods, I found UDP broadcast doesn't work between the pods.
What you expected to happen:
UDP broadcast to work.
How to reproduce it (as minimally and precisely as possible):
Start 2 pods -
where centos.yaml is -
On the first pod listen for UDP packets -
On the second pod send a UDP broadcast -
Note that nothing is received on the first pod.
Anything else we need to know?:
The same test does work in minikube. I see -
Environment:
kind version
):v0.5.1
kubectl version
):docker info
):/etc/os-release
):MacOS 10.15
The text was updated successfully, but these errors were encountered: