Infrastructure details Documentation End-To-End Testing Framework Introduction Running End-To-End Tests Test Reports Best Practices for Writing Tests Ginkgo Extensions Debugging: Running End-To-End Tests In following command to validate that your cluster has proper network connectivity: $ cilium connectivity test ℹ Monitor aggregation detected, will skip some flow validation steps � [k8s-cluster] Creating namespace ------------------------------------------------ ---------------------------------------------- ? Test Report ----------------------------------------------------------------------- ------------------

Infrastructure details Documentation End-To-End Testing Framework Introduction Running End-To-End Tests Test Reports Best Practices for Writing Tests Ginkgo Extensions Debugging: Running End-To-End Tests In following command to validate that your cluster has proper network connectivity: $ cilium connectivity test ℹ Monitor aggregation detected, will skip some flow validation steps � [k8s-cluster] Creating namespace ------------------------------------------------ ---------------------------------------------- ? Test Report ----------------------------------------------------------------------- ------------------

Infrastructure details Documentation End-To-End Testing Framework Introduction Running End-To-End Tests Test Reports Best Practices for Writing Tests Ginkgo Extensions Debugging: Running End-To-End Tests In the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. It is recommended to create a separate namespace for this. kubectl create ns cilium-test Deploy the check check with: kubectl apply -n cilium-test -f https://raw.githubusercontent.com/cilium/ci It will deploy a series of deployments which will use various connectivity paths to connect to each other. Connectivity

Infrastructure details Documentation End-To-End Testing Framework Introduction Running End-To-End Tests Test Reports Best Practices for Writing Tests Ginkgo Extensions Debugging: Running End-To-End Tests In the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. It is recommended to create a separate namespace for this. kubectl create ns cilium-test Deploy the check check with: kubectl apply -n cilium-test -f https://raw.githubusercontent.com/cilium/ci It will deploy a series of deployments which will use various connectivity paths to connect to each other. Connectivity

details Documentation Building End-To-End Testing Framework Introduction Running End-To-End Tests Test Reports Best Practices for Writing Tests Ginkgo Extensions Debugging: Running End-To-End Tests In 1/1 Running 0 13m Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent indicates the connectivity variant and the readiness and liveness gate indicates success or failure of the test: NAME READY STATUS RESTARTS AGE echo-a-5995597649-f5d5g

1/1 Running 0 13m Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent 1/1 Running 0 13m Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent cluster -n test-cluster -N 0 You should see something like this: [ℹ] using region us-west-2 [ℹ] setting availability zones to [us-west-2b us-west-2a us-west- 2c] [...] [✔] EKS cluster "test-cluster"

[h�p://cilium.readthedocs.io/en/latest/ge�ngstarted/minikube/#step-2- deploy-the-demo-applica�on] to test that the cluster is setup properly and that Cilium CNI and security policies are func�onal. Deleting the bas�on host. If kubectl isn’t installed on the bas�on host, you can login to the master node to test the below commands. You may need to copy the private key to the bas�on host to access the master node empire ship and xwing represents a similar service on an alliance ship. They exist so that we can test different security policies for access control to deathstar landing services. Applica�on Topology

0:* users:(("nc",pid=1289,fd=3)) $ nc -4 127.0.0.1 7777 hello⏎ hello ^D Netcat + /bin/cat Test it! Check open ports on VM external IP vm $ ip -4 addr show eth0 2: eth0: Test echo service on ports 7, 77, 777 $ { echo 'Hip'; sleep 0.1; } | nc -4 192.168.122.221 7 && g_tests/sk_lookup.c https://github.com/torvalds/linux/blob/v5.9/tools/testing/selftests/bpf/progs/test_sk_lookup.c ● “It’s crowded in here” blog post https://blog.cloudflare.com/its-crowded-in-here/

runtime issue on Arm64; • Multi-arch support for cilium-related images • CI/CD • Travis • Unit test Travis CI • Arm64 Full VM • arm64-graviton2 • Refer to: • https://docs.travis-ci.com/user/mu

"root=/dev/sda rw console=ttyS0,115200 acpi=off nokaslr" \ -serial stdio -display none Start the test VM cd /source/linux gdb build/vmlinux (gdb) target remote localhost:1234 (gdb) bpf/syscall.c:4180