-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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 controller load balancer can not connect to nodes #32556
Comments
Hi there, thanks for the bug report. It's not yet clear to me how exactly traffic is flowing. Could you outline the expected traffic flow, and indicate where you think it is failing? In particular, I suggest the section on troubleshooting with hubble to identify where packets are being dropped. Can you go through the troubleshooting section and clarify the problem a bit? Thanks. |
Also can you share your cilium configmap as well? Thanks. |
@squeed Ask any other question that you need if I still did not explain it well enough. Thanks for taking a look into this! |
@sayboras Yes, here it is:
Thank you for taking a look into this! |
Is there an existing issue for this?
What happened?
We have an EKS cluster where we are trying to use Cilium ingress controller and the load balancer created for the ingress can not always connect to the nodes.
What we see is that the load balancer can connect to some nodes during periods but is not a consistent behavior and there is no pattern between the nodes behind that it can connect and the ones that can not.
Checking directly in the nodes also connecting to the nodePort opened for the load balancer does not work so should not be a problem of security groups, anyway we tried opening traffic from every internal address and nothing, some nodes work and others not or even sometimes no nodes happen to be accessible by the load balancer.
I checked and all the nodes have this cilium LB configuration for the nodePort:
Configuration values used:
cni-config configmap values:
Cilium Version
We tried it in multiple versions:
Kernel Version
Linux 5.10.215-203.850.amzn2.aarch64
Kubernetes Version
v1.26.15
Regression
No response
Sysdump
Relevant log output
No response
Anything else?
No response
Cilium Users Document
Code of Conduct
The text was updated successfully, but these errors were encountered: