Run connectivity tests based on nodeSelector #1269
Assignees
Labels
kind/feature
New feature or request
Comments
|
might solve #1129 as well |
tklauser
added a commit
that referenced
this issue
Mar 9, 2023
…ctor
The connectivity test pods will be restricted to nodes matching labels
given in the --node-selector flag.
Usage:
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
kind-control-plane Ready control-plane 15m v1.25.3
kind-worker Ready <none> 15m v1.25.3
kind-worker2 Ready <none> 15m v1.25.3
kind-worker3 Ready <none> 15m v1.25.3
kind-worker4 Ready <none> 15m v1.25.3
$ kubectl label nodes kind-worker{2,3} connectivity.cilium.io/test=true
$ cilium connectivity test --node-selector connectivity.cilium.io/test=true
[...]
✅ All 32 tests (261 actions) successful, 2 tests skipped, 1 scenarios skipped.
$ kubectl get pods -n cilium-test -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
client-7858556799-xd52x 1/1 Running 0 5m56s 10.244.2.120 kind-worker3 <none> <none>
client2-646989676f-zgxxl 1/1 Running 0 5m56s 10.244.2.55 kind-worker3 <none> <none>
echo-other-node-79659b5c6-8dzfw 2/2 Running 0 5m55s 10.244.3.148 kind-worker2 <none> <none>
echo-same-node-69f7699d84-5bvxj 2/2 Running 0 5m56s 10.244.2.168 kind-worker3 <none> <none>
Fixes #1269
Signed-off-by: Tobias Klauser <[email protected]>
tklauser
added a commit
that referenced
this issue
Mar 14, 2023
…ctor
The connectivity test pods will be restricted to nodes matching labels
given in the --node-selector flag.
Usage:
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
kind-control-plane Ready control-plane 15m v1.25.3
kind-worker Ready <none> 15m v1.25.3
kind-worker2 Ready <none> 15m v1.25.3
kind-worker3 Ready <none> 15m v1.25.3
kind-worker4 Ready <none> 15m v1.25.3
$ kubectl label nodes kind-worker{2,3} connectivity.cilium.io/test=true
$ cilium connectivity test --node-selector connectivity.cilium.io/test=true
[...]
✅ All 32 tests (261 actions) successful, 2 tests skipped, 1 scenarios skipped.
$ kubectl get pods -n cilium-test -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
client-7858556799-xd52x 1/1 Running 0 5m56s 10.244.2.120 kind-worker3 <none> <none>
client2-646989676f-zgxxl 1/1 Running 0 5m56s 10.244.2.55 kind-worker3 <none> <none>
echo-other-node-79659b5c6-8dzfw 2/2 Running 0 5m55s 10.244.3.148 kind-worker2 <none> <none>
echo-same-node-69f7699d84-5bvxj 2/2 Running 0 5m56s 10.244.2.168 kind-worker3 <none> <none>
Fixes #1269
Signed-off-by: Tobias Klauser <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the ability to run the connectivity tests between two node groups might be useful as the user might want to test different configurations in those two node groups to make sure that this new configuration passes all tests before applying it to the rest of the cluster.
The text was updated successfully, but these errors were encountered: