Observability Kubernetes Integration Multi-Cluster (Cluster Mesh) Getting Help FAQ Slack GitHub Training Enterprise support Security Bugs Operations System Requirements Summary Architecture Support Linux Distribution Example Prometheus & Grafana Deployment Metrics Reference Performance & Scalability Tuning Guide CNI Performance Benchmark Scalability Troubleshooting Component & Cluster Health Observing Flows with Hubble resources (CRDs). If you run a cluster with more pods and more nodes than the ones tested in the Scalability report. Requirements Make sure your Kubernetes environment is meeting the requirements: Kubernetes

Observability Kubernetes Integration Multi-Cluster (Cluster Mesh) Getting Help FAQ Slack GitHub Training Enterprise support Security Bugs Operations System Requirements Summary Linux Distribution Compatibility Example Prometheus & Grafana Deployment Metrics Reference Performance & Scalability Tuning Guide CNI Performance Benchmark Scalability Troubleshooting Component & Cluster Health Observing Flows with Hubble end-kubernetes/compute-storage-net/network-plugins/#support-traffic- shaping] plugin. Due to scalability concerns in particular for multi-queue network interfaces, it is not recommended to use the bandwidth

Observability Kubernetes Integration Multi-Cluster (Cluster Mesh) Getting Help FAQ Slack GitHub Training Enterprise support Security Bugs Operations System Requirements Summary Linux Distribution Compatibility Hubble Metrics Example Prometheus & Grafana Deployment Metrics Reference Scalability Limiting Identity-Relevant Labels Scalability report Performance Evaluation Setup Evaluation Results Tuning Troubleshooting allocation remains to be CRD-based which means that etcd remains an optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce

allocation remains to be CRD-based which means that etcd remains an optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce specified with the -- cluster-name=NAME argument or cluster-name ConfigMap option. To ensure scalability of identity allocation and policy enforcement, each cluster continues to manage its own security enabled. Roadmap Ahead Future versions will put an API server before etcd to provide better scalability and simplify the installation to support any etcd support Introduction of IPsec and use of ESP

allocation remains to be CRD-based which means that etcd remains an optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce specified with the -- cluster-name=NAME argument or cluster-name ConfigMap option. To ensure scalability of identity allocation and policy enforcement, each cluster continues to manage its own security enabled. Roadmap Ahead Future versions will put an API server before etcd to provide better scalability and simplify the installation to support any etcd support Introduction of IPsec and use of ESP

Hubble Metrics Example Prometheus & Grafana Deployment Metrics Reference Scalability Limiting Identity-Relevant Labels Scalability report Performance Evaluation Setup Evaluation Results Tuning Troubleshooting allocation remains to be CRD-based which means that etcd remains an optional component to improve scalability. Failures in providing etcd will not be critical to the availability of Cilium but will reduce specified with the -- cluster-name=NAME argument or cluster-name ConfigMap option. To ensure scalability of identity allocation and policy enforcement, each cluster continues to manage its own security

specified with the --cluster-name=NAME argument or cluster-name ConfigMap op�on. To ensure scalability of iden�ty alloca�on and policy enforcement, each cluster con�nues to manage its own security iden�ty encryp�on enabled. Roadmap Ahead Future versions will put an API server before etcd to provide be�er scalability and simplify the installa�on to support any etcd support Introduc�on of IPSec and use of ESP or services like Twilio or Stripe as well as accessing private APIs that are hosted elsewhere in your enterprise datacenter or cloud deployment. In the Direct / Na�ve Rou�ng Mode mode described before, if container