-
Notifications
You must be signed in to change notification settings - Fork 118
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
Add connection test #1012
Comments
/triage accepted |
@Rozzii: 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. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle frozen |
We don't currently have a specific test that checks if pods can reach each other (on the same or a different node). Of course many tests will fail if there are connection issues between pods/nodes, but it can be hard to debug and conclude that the issue is coming from network issues. Therefore I suggest adding a test specifically for this.
We could for example use mirantis k8s-netchecker to ensure the network is operational in the workload cluster.
The text was updated successfully, but these errors were encountered: