Same as test-conn-disrupt for E/W traffic, run test-conn-disrupt for NodePort from the clients running on the --nodes-without-cilium nodes.

Obsolete info

The migrate-svc which is used in the test/k8sT/Updates.go suite is used to test whether during the cilium-agent upgrade no established connectivity to the migrate-svc svc is broken.

Currently, the svc is of the ClusterIP type, so on net-next it only tests E-W case handled by bpf_sock which does the xlation only once before the connection is established, and therefore it's very unlikely to spot any issues in the service xlation happening during the upgrade.

We should extend the test by changing the svc type to NodePort, and in addition to the ClusterIP case, establish connections from a node which is not handled by Cilium (on the net-next job it's k8s3). This would test the other svc xlation path (lb4_lookup_service() -> lb4_local() -> ct_lookup4()). Also, having this case would have prevented from #13529 problem.