-
Notifications
You must be signed in to change notification settings - Fork 132
Add connection test #1012
Copy link
Copy link
Open
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.
Description
Metadata
Metadata
Assignees
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Backlog
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.