Concepts: Describes the components of Cilium, and the different models for deploying Cilium. Provides the high-level understanding required to run a full Cilium deployment and understand its behavior. Architecture: optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce the efficacy of state propagation. This allows the managed etcd to recover functionality. If you are running in an environment with more than 250 nodes, 5k pods, or if you observe a high overhead in state propagation caused by Kubernetes events. If you do not want Cilium to store state

Concepts: Describes the components of Cilium, and the different models for deploying Cilium. Provides the high-level understanding required to run a full Cilium deployment and understand its behavior. Installation repositories Update cilium-builder and cilium-runtime images Nightly Docker image Code Overview High-level Cilium Hubble Important common packages Debugging toFQDNs and DNS Debugging Mutexes / Locks kvstore: If you are running in an environment with more than 250 nodes, 5k pods, or if you observe a high overhead in state propagation caused by Kubernetes events. If you do not want Cilium to store state

Concepts: Describes the components of Cilium, and the different models for deploying Cilium. Provides the high-level understanding required to run a full Cilium deployment and understand its behavior. Architecture: optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce the efficacy of state propagation. This allows the managed etcd to recover functionality. If you are running in an environment with more than 250 nodes, 5k pods, or if you observe a high overhead in state propagation caused by Kubernetes events. If you do not want Cilium to store state

Concepts: Describes the components of Cilium, and the different models for deploying Cilium. Provides the high-level understanding required to run a full Cilium deployment and understand its behavior. Installation repositories Update cilium-builder and cilium-runtime images Nightly Docker image Code Overview High-level Cilium Hubble Important common packages Debugging toFQDNs and DNS Debugging Mutexes / Locks optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce the efficacy of state propagation. This allows the managed etcd to recover

Concepts: Describes the components of Cilium, and the different models for deploying Cilium. Provides the high-level understanding required to run a full Cilium deployment and understand its behavior. Installation cilium-builder and cilium-runtime images Nightly Docker image Image Building Process Code Overview High-level Cilium Hubble Important common packages Debugging toFQDNs and DNS Debugging Mutexes / Locks a list of reasons when to use a kvstore: If you are running in an environment where you observe a high overhead in state propagation caused by Kubernetes events. If you do not want Cilium to store state

Concepts: Describes the components of Cilium, and the different models for deploying Cilium. Provides the high-level understanding required to run a full Cilium deployment and understand its behavior. Installation release images Update cilium-builder and cilium-runtime images Nightly Docker image Code Overview High-level Cilium Hubble Important common packages Debugging toFQDNs and DNS Debugging Mutexes / Locks optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce the efficacy of state propagation. This allows the managed etcd to recover

Concepts: Describes the components of Cilium, and the different models for deploying Cilium. Provides the high-level understanding required to run a full Cilium deployment and understand its behavior. Architecture: create cluster You should see something like this: [ℹ] using region us-west-2 [ℹ] setting availability zones to [us-west-2b us-west-2a us-west-2c] [ℹ] subnets for us-west-2b - public:192.168.0.0/19 eu-west-1b,eu-west-1c : The 3 zones ensure the HA of master nodes, each belonging in a different Availability zones. --zones eu-west-1a,eu-west-1b,eu-west-1c : Zones where the worker nodes will be deployed