managed by Cilium, similar to the steps that we have previously performed for kube- dns $ kubectl delete pods -n kube-system $(kubectl get pods -n kube-system -o custom-columns=NAME:.metadata.name,HOSTNETWORK: kops cluster creation, use kops to destroy a cluster immediately with the parameter --yes: kops delete cluster ${NAME} --yes Appendix: Details of kops flags used in cluster creation The following section emo- application] to deploy a demo application and verify the correctness of the installation. Delete Cluster $ cd contrib/terraform/aws $ terraform destroy Installation using kubeadm Instructions

original GKE network plugin. Restart kube-dns to ensure it is managed by Cilium. kubectl -n kube-system delete pod -l k8s-app=kube-dns Deploy Cilium + cilium-etcd-operator The following all-in-one YAML will managed by Cilium, similar to the steps that we have previously performed for kube-dns $ kubectl delete pods -n kube-system $(kubectl get pods -n kube-system -o pod "event-exporter-v0.2.3-f9c896d75-cbvcz" kops cluster crea�on, use kops to destroy a cluster immediately with the parameter --yes : kops delete cluster ${NAME} --yes Appendix: Details of kops flags used in cluster creation The following sec�on

hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" [us-west-2b us-west-2a us-west- 2c] [...] [✔] EKS cluster "test-cluster" in "us-west-2" region is ready Delete VPC CNI (aws-node DaemonSet) Cilium will manage ENIs instead of VPC CNI, so the aws-node DaemonSet Note Once aws-node DaemonSet is deleted, EKS will not try to restore it. kubectl -n kube-system delete daemonset aws-node Prepare & Deploy Cilium Note First, make sure you have Helm 3 installed [https://helm

tables. The issues can be fixed by restarting all pods, alternatively to avoid such issues you can delete aws-node DaemonSet prior to installing Cilium. OpenShift To install Cilium on OpenShift [https://www hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" to be scheduled successfully. Once done with the test, remove the cilium-test namespace: kubectl delete ns cilium-test Next Steps Setting up Hubble Observability Inspecting Network Flows with the CLI

tables. The issues can be fixed by restarting all pods, alternatively to avoid such issues you can delete aws-node DaemonSet prior to installing Cilium. OpenShift To install Cilium on OpenShift [https://www hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" to be scheduled successfully. Once done with the test, remove the cilium-test namespace: kubectl delete ns cilium-test Next Steps Setting up Hubble Observability Inspecting Network Flows with the CLI

hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" after connectivity test Remove cilium-test namespace: kubectl delete ns cilium-test Remove SecurityContextConstraints: kubectl delete scc cilium-test Managed Kubernetes The following guides cover

hostNetwork --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" after connectivity test Remove cilium-test namespace: kubectl delete ns cilium-test Remove SecurityContextConstraints: kubectl delete scc cilium-test Managed Kubernetes The following guides cover [us-west-2b us-west-2a us-west- 2c] [...] [✔] EKS cluster "test-cluster" in "us-west-2" region is ready Delete VPC CNI (aws-node DaemonSet) Cilium will manage ENIs instead of VPC CNI, so the aws-node DaemonSet