Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Unable to connect to service from local network after livenessProbe has been started #56887
Is this a BUG REPORT or FEATURE REQUEST?:
kubectl get nodes
I've the test pod with service
After launch, the pod started on dsdocker01 node and I can connect to corresponding port number by any host from my local network
After initialDelaySeconds livenessProbe has been started and I can not connect from local network to corresponding port of node where pod is working. But I still can connect to this port on other kubernetes nodes:
tcpdump output from container:
It seems that container just do not answer on this packets
Also i can reach this port locally from a corresponding kubernters node:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
It's not clear to me what that tcpdump is showing - traffic between 2 containers on a single node? Via nodeport or direct? Dumping from which namespace?
On Thu, Mar 22, 2018 at 9:02 AM rogovst ***@***.***> wrote: net.ipv4.tcp_tw_recycle = 1 - is my problem. After remove that setting everything works as expected Please close the issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#56887 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVK0s7mVnxw5JUpRpMzIJZam2goP2ks5tg8r5gaJpZM4Q388K> .