Kubernetes environment. Deploy Cilium + cilium-etcd-operator Download the Cilium release tarball and change to the kubernetes install directory: curl -LO https://github.com/cilium/cilium/archive/v1.6.tar ConfigMap. Download the base YAML and configure it with Helm: Download the Cilium release tarball and change to the kubernetes install directory: curl -LO https://github.com/cilium/cilium/archive/v1.6.tar sh/docs/using_helm/#install-helm] to prepare generating the deployment artifacts based on the Helm templates. Change the etcd endpoints accordingly: helm template cilium \ --namespace kube-system \ --set global

the eksctl Documenta�on [h�ps://github.com/weaveworks/eksctl] for details on how to set creden�als, change region, VPC, cluster size, etc. eksctl create cluster You should see something like this: [ℹ] [h�ps://cloud.google.com/sdk/]. This guide will create a cluster on zone europe-west4-a ; feel free to change the zone if you are in a different region of the globe. export GKE_ZONE="europe-west4-a" gcloud dedicated S3 bucket in order to store the state and representa�on of the cluster. You will need to change the bucket name and provide your unique bucket name (for example a reverse of FQDN added with short

possible before. It does so in a completely transparent way, without requiring the application to change in any way. eBPF is equally well-equipped to handle modern containerized workloads as well as more the RKE Installation Guide [https://rancher.com/docs/rke/latest/en/installation/] with the below change: From: network: options: flannel_backend_type: "vxlan" plugin: "canal" To: network: plugin: the RKE Installation Guide [https://rancher.com/docs/rke/latest/en/installation/] with the below change: From: network: options: flannel_backend_type: "vxlan" plugin: "canal" To: network: plugin:

API Rate Limiting Default Rate Limits Configuration Automatic Adjustment Metrics Understanding the log output Configuration Core Agent Monitoring & Metrics Installation cilium-agent cilium-operator control-plane - role: worker - role: worker - role: worker networking: disableDefaultCNI: true To change the version of kubernetes being run, image has to be defined for each node. See the Node Configration identityAllocationMode=kvstore \ --set global.cluster.name=cluster2 \ --set global.cluster.id=2 Change the kubectl context to kind-cluster1 cluster: kubectl config use-context kind-cluster1 helm install

possible before. It does so in a completely transparent way, without requiring the application to change in any way. eBPF is equally well-equipped to handle modern containerized workloads as well as more the RKE Installation Guide [https://rancher.com/docs/rke/latest/en/installation/] with the below change: From: network: options: flannel_backend_type: "vxlan" plugin: "canal" To: network: plugin: the RKE Installation Guide [https://rancher.com/docs/rke/latest/en/installation/] with the below change: From: network: options: flannel_backend_type: "vxlan" plugin: "canal" To: network: plugin:

possible before. It does so in a completely transparent way, without requiring the application to change in any way. BPF is equally well-equipped to handle modern containerized workloads as well as more By default, the latest version of Kubernetes from when the kind release was created is used. To change the version of Kubernetes being run, image has to be defined for each node. See the Node Configuration identityAllocationMode=kvstore \ --set global.cluster.name=cluster2 \ --set global.cluster.id=2 Change the kubectl context to kind-cluster1 cluster: kubectl config use-context kind-cluster1 helm install

possible before. It does so in a completely transparent way, without requiring the application to change in any way. eBPF is equally well-equipped to handle modern containerized workloads as well as more By default, the latest version of Kubernetes from when the kind release was created is used. To change the version of Kubernetes being run, image has to be defined for each node. See the Node Configuration --set identityAllocationMode=kvstore \ --set cluster.name=cluster2 \ --set cluster.id=2 Change the kubectl context to kind-cluster1 cluster: kubectl config use-context kind-cluster1 helm install