Introduction

When working with Crusoe Managed Kubernetes (CMK) Cluster, there can be different scenarios where one would need to determine the number of allocated IPs from the IPAM (subnet from which Cilium is allocating pod IP addresses) like

• Capacity planning – Ensure enough IPs are available for current/future pods.

• Troubleshooting – Diagnose issues like pods failing to start due to IP exhaustion.

• Leak detection – Identify IPs not released after pod deletion.

• Cluster insight – Understand workload scaling and IP usage patterns.

• Config validation – Confirm IPAM is using the right ranges efficiently.

Prerequisites

Before starting, ensure you have the following:

• Access to a Crusoe Cloud project with appropriate permissions
• A CMK cluster with the latest image version (>= 1.30.8-cmk.26)
• Kubeconfig to access your CMK cluster

Step-by-Step Instructions

Run kubectl command to find the cilium-agent pod and to run the Cilium CLI's status command:

kubectl exec -it $(kubectl get pods -n kube-system -l k8s-app=cilium \
-o jsonpath='{.items[0].metadata.name}') -n kube-system -c cilium-agent -- \
cilium-dbg status | grep IPAM

Example:

$ kubectl exec -it $(kubectl get pods -n kube-system -l k8s-app=cilium \
-o jsonpath='{.items[0].metadata.name}') -n kube-system -c cilium-agent -- \
cilium-dbg status | grep IPAM

IPAM:          IPv4: 28/254 allocated from 10.234.0.0/24,

Note that running command cilium-dbg status --verbose provides detailed overview of the agent's health, allocated addresses, IPAM usage, cluster health, BPF maps, policy enforcement, networking mode, hubble status etc.

Additional Resources

Cilium DBG Status CLI