the following steps: Default Configuration: Datapath IPAM Datastore Direct Routing Kubernetes PodCIDR Kubernetes CRD Datapath IPAM Datastore Requirements: The cluster should be created with the taint ni? tabs=azure-cli] mode, perform the following steps: Default Configuration: Datapath IPAM Datastore Encapsulation Cluster Pool Kubernetes CRD Note BYOCNI is the preferred way to run Cilium on AKS integration via Azure IPAM, perform the following steps: Default Configuration: Datapath IPAM Datastore Direct Routing Azure IPAM Kubernetes CRD Note Azure IPAM offers integration with the Azure stack

google.com/kubernetes- engine], perform the following steps: Default Configuration: Datapath IPAM Datastore Direct Routing Kubernetes PodCIDR Kubernetes CRD Requirements: The cluster should be created ni? tabs=azure-cli] mode, perform the following steps: Default Configuration: Datapath IPAM Datastore Encapsulation Cluster Pool Kubernetes CRD Note BYOCNI is the preferred way to run Cilium on AKS integration via Azure IPAM, perform the following steps: Default Configuration: Datapath IPAM Datastore Direct Routing Azure IPAM Kubernetes CRD Note Azure IPAM offers integration with the Azure stack

"plugins": [ { "type": "calico", "log_level": "info", "datastore_type": "kubernetes", "mtu": 1440, "ipam": { "type": "calico-ipam" information of the Cilium daemon and related components such as the local container runtime, connected datastore, Kubernetes integration. Status Codes: Request Headers: Status Codes: Status Codes: 200 OK

"plugins": [ { "type": "calico", "log_level": "info", "datastore_type": "kubernetes", "mtu": 1440, "ipam": { "type": "calico-ipam" information of the Cilium daemon and related components such as the local container runtime, connected datastore, Kubernetes integration. Status Codes: Request Headers: Status Codes: Status Codes: 200 OK

"plugins": [ { "type": "calico", "log_level": "info", "datastore_type": "kubernetes", "mtu": 1440, "ipam": { "type": "calico-ipam" information of the Cilium daemon and related components such as the local container runtime, connected datastore, Kubernetes integration and Hubble. Status Codes: Request Headers: Status Codes: Status Codes:

根据Cilium endpoint 的 label， 计算生成集群唯一的identity，意味着 pod 的 IP 变更，不需要引起 policy 信息的同步，有效降低信息同步频率。 • 多个相同policy策略的endpoint可以共用一个identity，例如同一 deployment 下的多个pod副本 share 相同的 identity，这意味着集群中可以有效降低 policy 的数量。 pod1

"plugins": [ { "type": "calico", "log_level": "info", "datastore_type": "kubernetes", "mtu": 1440, "ipam": { "type": "calico-ipam" information of the Cilium daemon and related components such as the local container runtime, connected datastore, Kubernetes integration and Hubble. Status Codes: Request Headers: Status Codes: Status Codes:

informa�on of the Cilium daemon and related components such as the local container run�me, connected datastore, Kubernetes integra�on. Status Codes 200 OK [h�p://www.w3.org/Protocols/rfc2616/rfc2616- sec10