1.10 kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent 5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam kubectl create -f https://raw.githubusercontent config Install etcd Install etcd as a StatefulSet into your new Kubernetes cluster. kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam Install Cilium Install Cilium as a DaemonSet

requirements of Cilium >= 1.6.0. minikube version minikube version: v1.3.1 commit: ca60a424ce69a4d79f502650199ca2b52f29e631 3. Create a minikube cluster: minikube start --network-plugin=cni --memory=4096 4. cluster. The DaemonSet will automatically install itself as Kubernetes CNI plugin. kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.6/inst Validate the Installation You can monitor connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1.6/examp It will deploy a simple probe and echo server

requirements of Cilium >= 1.6.0. minikube version minikube version: v1.3.1 commit: ca60a424ce69a4d79f502650199ca2b52f29e631 3. Create a minikube cluster: minikube start --network-plugin=cni --memory=4096 4. cluster. The DaemonSet will automatically install itself as Kubernetes CNI plugin. kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.7/inst Validate the Installation You can monitor connectivity test You can deploy the “connectivity-check” to test connectivity between pods. kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1.7/examp It will deploy a series of deployments which

requirements of Cilium >= 1.6.0. minikube version minikube version: v1.3.1 commit: ca60a424ce69a4d79f502650199ca2b52f29e631 3. Create a minikube cluster: minikube start --network-plugin=cni --memory=4096 # Only customization. In case of installing Cilium with CRIO, please see CRIO instructions. kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.8/inst Warning experimental-install.yaml is a pre-rendered to try out experimental features, It should only be used in testing environments. kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.8/inst Validate the Installation You can monitor

Cilium code or documentation. A hands-on tutorial [https://play.instruqt.com/isovalent/invite/j4maqox5r1h5] in a live environment is also available for users looking for a way to quickly get started and experiment requirements of Cilium >= 1.6.0. minikube version minikube version: v1.3.1 commit: ca60a424ce69a4d79f502650199ca2b52f29e631 3. Create a minikube cluster: minikube start --network-plugin=cni --memory=4096 Note customization. In case of installing Cilium with CRIO, please see CRIO instructions. kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.9/inst With experimental-install.yaml Warning

Cilium code or documentation. A hands-on tutorial [https://play.instruqt.com/isovalent/invite/j4maqox5r1h5] in a live environment is also available for users looking for a way to quickly get started and experiment "node.cilium.io/agent-not-ready" value: "true" effect: "NoExecute" EOF eksctl create cluster -f ./eks-config.yaml Note Please make sure to read and understand the documentation page on taint effects kube-system/event-exporter-gke-564fb97f9- rv8hg ♻ Restarted unmanaged pod kube-system/kube-dns-6465f78586-hlcrz ♻ Restarted unmanaged pod kube-system/kube-dns-autoscaler- 7f89fb6b79-fsmsg ♻ Restarted unmanaged

Cilium code or documentation. A hands-on tutorial [https://play.instruqt.com/isovalent/invite/j4maqox5r1h5] in a live environment is also available for users looking for a way to quickly get started and experiment "node.cilium.io/agent-not-ready" value: "true" effect: "NoExecute" EOF eksctl create cluster -f ./eks-config.yaml Note Please make sure to read and understand the documentation page on taint effects kube-system/event-exporter-gke-564fb97f9- rv8hg ♻ Restarted unmanaged pod kube-system/kube-dns-6465f78586-hlcrz ♻ Restarted unmanaged pod kube-system/kube-dns-autoscaler- 7f89fb6b79-fsmsg ♻ Restarted unmanaged

need… ❏ VM running Linux kernel 5.9+ ❏ bpftool 5.9+ ❏ libbpf headers ❏ kernel headers vm $ uname -r 5.9.1-36.vanilla.1.fc32.x86_64 vm $ bpftool version bpftool v5.9.1 Code and instructions at https://github bpftool prog show pinned /sys/fs/bpf/echo_dispatch_prog 75: sk_lookup name echo_dispatch tag 77fd96f660a5d2ab gpl loaded_at 2020-10-23T09:36:45+0000 uid 0 xlated 304B jited 197B memlock

What are we going to build? eBPF [0] % objdump --syms app|grep computeE 00000000006609a0 g F .text 000000000000004b main.computeE [0] % objdump -d app | less 00000000006609a0 00 mov $0x2,%ecx 6609aa: f2 0f 10 05 16 a6 0f movsd 0xfa616(%rip),%xmm0 6609b1: 00 6609b2: f2 0f 10 0d 36 a6 0f movsd 0xfa636(%rip),%xmm1 Diving into the .. main.computeE 0x6609a0 { App Binary main.main { 0x6609f0 ... ... main.computeE Uprobe Hook { App Binary main.main { 0x6609f0 BPF Program Perf Buffer Tracer Binary What does the BPF

implementation: mem:[:access] [Hardware breakpoint] Example: perf stat -e mem:0xffffffffbb65f478:rw 01 https://www.kernel.org/doc/ols/2009/ols2009-pages-149-158.pdf Implementation void bpf kernel_stack_id = stack_traces.get_stackid(ctx, 0); key.user_stack_id = stack_traces.get_stackid(ctx, BPF_F_USER_STACK); u64 zero = 0, *val; val = counts.lookup_or_init(&key, &zero); (*val)++; bpf_trace_printk("Hello