```# cilium status KVStore: Ok D...
# k3s
l
Copy code
# cilium status
KVStore:                 Ok   Disabled
Kubernetes:              Ok   1.23 (v1.23.6+k3s1) [linux/amd64]
Kubernetes APIs:         ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumEndpoint", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "<http://networking.k8s.io/v1::NetworkPolicy|networking.k8s.io/v1::NetworkPolicy>"]
KubeProxyReplacement:    Strict    [bond0.3196 100.100.230.10 (Direct Routing), bond0.3198 100.100.232.8]
Host firewall:           Enabled   [bond0.3196, bond0.3198]
CNI Chaining:            none
Cilium:                  Ok   1.12.2 (v1.12.2-c7516b9)
NodeMonitor:             Listening for events on 80 CPUs with 64x4096 of shared memory
Cilium health daemon:    Ok
IPAM:                    IPv4: 88/254 allocated from 10.247.0.0/24,
c
yes, cilum does not respect the node PodCIDR assignments, it has its own IPAM system. There are multiple CNIs that handle IPAM on their own.
l
Thanks!