on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare filesystem mounted on all worker nodes Enable PodCIDR allocation (--allocate-node-cidrs) in the kube- controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare

on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run

on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare terway-eni terway-eniip Note If you are using ACK with Flannel (DaemonSet kube-flannel-ds), the Cloud Controller Manager (CCM) will create route (Pod CIDR) in VPC. If your cluster is an Managed Kubernetes you show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run

on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run

on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare terway-eni terway-eniip Note If you are using ACK with Flannel (DaemonSet kube-flannel-ds), the Cloud Controller Manager (CCM) will create route (Pod CIDR) in VPC. If your cluster is an Managed Kubernetes you show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run

on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare ion labels any:!pod-template-hash Ignore all pod-template-hash labels any:!controller-revision-hash Ignore all controller-revision-hash labels any:!annotation.* Ignore all annotation labels any:!etcd_node

filesystem mounted on all worker nodes Enable PodCIDR alloca�on ( --allocate-node-cidrs ) in the kube-controller-manager (recommended) Refer to the sec�on Requirements for detailed instruc�on on how to prepare filesystem mounted on all worker nodes Enable PodCIDR alloca�on ( --allocate-node-cidrs ) in the kube-controller-manager (recommended) Refer to the sec�on Requirements for detailed instruc�on on how to prepare NodeMonitor: Listening for events on 1 CPUs with 64x4096 of sha Cilium health daemon: Ok Controller Status: 6/6 healthy Proxy Status: OK, ip 10.15.28.238, port-range 10000-20000 Cluster

cilium-operator Node #1 cilium-agent cilium-operator Control Plane kube-api-server cilium-agent kube-controller- manager scheduler ….. etcd VPC digitalocean.com How’s Cilium been working for us? ● Good