-
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
Network policies blocking probes #10030
Comments
Possible duplicate of |
I tried with k3s v1.28.9 and it's been fixed. |
Closing as duplicate/symptom of #9925 |
Confirmed, upgraded the cluster to v1.29.4+k3s1 this morning and this issue no longer happens. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
K3s Version: v1.28.8+k3s1
Node(s) CPU architecture, OS, and Version:
Linux s3 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux
Cluster Configuration:
3 servers, dual stack, ipv6 primary. Using default flannel.
Describe the bug:
Network policy blocks probes.
Steps To Reproduce:
Deploy this test deployment:
You should fairly quickly see the nginx pod's startup probe fail:
The nginx log appears fine, and indeed you can see no probe hitting it:
Now delete that network policy:
You'll immediately starting seeing the probes hit nginx:
I believe the probes should be considered internal to the network namespace of the pod, and thus shouldn't be effected by the network policies at all, but that doesn't appear to be the case here. Any idea what's going on?
The text was updated successfully, but these errors were encountered: