release Testing CI / Jenkins Jobs Overview Triggering Pull-Request Builds With Jenkins Using Jenkins for testing CI Failure Triage Infrastructure details Documentation End-To-End Testing Framework Running End-To-End Tests In Other Environments via SSH VMs for Testing Further Assistance Unit Testing Prerequisites Running all tests Testing individual packages Running individual tests Automatically run Hardening Offloads Toolchain Development Environment LLVM iproute2 bpftool BPF sysctls Kernel Testing JIT Debugging Introspection Tracing pipe Miscellaneous Program Types XDP tc (traffic control)

date For the final release Testing CI / Jenkins Jobs Overview Triggering Pull-Request Builds With Jenkins Testing with race condition detection enabled Using Jenkins for testing CI Failure Triage Infrastructure 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 Tests In Other Environments via SSH VMs for Testing VM images Known Issues and Workarounds Further Assistance Unit Testing Prerequisites Running all tests Testing individual packages Running individual tests

release Testing CI / Jenkins Jobs Overview Triggering Pull-Request Builds With Jenkins Using Jenkins for testing CI Failure Triage Infrastructure details Documentation Building End-To-End Testing Framework Running End-To-End Tests In Other Environments via SSH VMs for Testing Further Assistance Unit Testing Prerequisites Running all tests Testing individual packages Running individual tests Automatically run Hardening Offloads Toolchain Development Environment LLVM iproute2 bpftool BPF sysctls Kernel Testing JIT Debugging Introspection Tracing pipe Miscellaneous Program Types XDP tc (traffic control)

date For the final release Testing CI / Jenkins Jobs Overview Triggering Pull-Request Builds With Jenkins Testing with race condition detection enabled Using Jenkins for testing CI Failure Triage Infrastructure 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 Tests In Other Environments via SSH VMs for Testing VM images Known Issues and Workarounds Further Assistance Unit Testing Prerequisites Running all tests Testing individual packages Running individual tests

Developer / Contributor Guide Setting up the development environment Development process End-To-End Testing Framework How to contribute Pull request review process Building Container Images Documentation Developer’s process CI / Jenkins Jobs Overview Triggering Pull-Request Builds With Jenkins Using Jenkins for testing CI Failure Triage Infrastructure details BPF and XDP Reference Guide BPF Architecture Toolchain prompted to create a ssh public-private key pair. ssh-keygen (Please see Deleting a Cluster) Testing Cilium Follow the Cilium getting started guide example [http://cilium.readthedocs.io/en/latest

date For the final release Testing CI / Jenkins Jobs Overview Triggering Pull-Request Builds With Jenkins Testing with race condition detection enabled Using Jenkins for testing CI Failure Triage Infrastructure 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 Other Environments via SSH VMs for Testing VM images Known Issues and Workarounds Further Assistance Integration Testing Prerequisites Running all tests Testing individual packages Running individual

be prompted to create a ssh public-private key pair. ssh-keygen (Please see Dele�ng a Cluster) Testing Cilium Follow the Cilium ge�ng started guide example [h�p://cilium.readthedocs.io/en/latest/ge� following pod can be created for debugging purposes: apiVersion: v1 kind: Pod metadata: name: testing-aws-pod namespace: kube-system spec: containers: - name: aws-cli image: mesosphere/aws-cli available AWS instances, the following command can be used: $ kubectl -n kube-system exec -ti testing-aws-pod -- aws ec2 describe-inst Once the secret has been created and validated, the cilium-operator