> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Note About Cilium CLI
> Explains difference between the local Cilium CLI used for installation and cluster management and the in‑pod cilium/cilium-dbg tools used for in-cluster diagnostics and debugging
So before we proceed, a quick clarification about the Cilium command-line tools — this often causes confusion later when working with clusters.
There are two separate command-line tools that share the name "cilium," but they serve different purposes and run in different environments:
* A local Cilium CLI binary you install on your workstation. It is used for installing Cilium on a cluster and for higher-level management and checks (for example, `cilium install` and `cilium status`).
* One or more Cilium binaries that run inside Cilium agent pod(s) in the cluster. These in-pod tools — commonly `cilium` and `cilium-dbg` — are focused on in-cluster diagnostics and advanced debugging.
These are distinct tools even though they share the same command name. Use the local CLI for installation and cluster-level checks; use the in-pod binaries for deep debugging and diagnostics inside the cluster.
Comparison at a glance:
| Tool | Primary scope | Typical location | Common examples |
| ------------------------------ | ------------------------------------------------ | -------------------------------------- | ------------------------------------------- |
| Local Cilium CLI | Install, upgrade, and basic cluster-level checks | Your workstation / CI runner | `cilium install`, `cilium status` |
| In-pod `cilium` / `cilium-dbg` | Deep diagnostics, runtime troubleshooting | Inside Cilium agent pods (kube-system) | `cilium status` (in-pod), `cilium-dbg help` |
Examples of common commands
Local machine (installer / management CLI)
```bash theme={null}
# Install Cilium onto the current kubeconfig cluster
cilium install
# Check cluster-level Cilium status from your workstation
cilium status
```
Inside a Cilium pod (advanced debug / diagnostic tools)
```bash theme={null}
# Run the in-pod 'cilium' binary for status or diagnostics
kubectl -n kube-system exec -it -- cilium status
# Use the dedicated debug binary inside the pod
kubectl -n kube-system exec -it -- cilium-dbg help
```
Key takeaway: treat the local CLI and the in-pod binaries as separate tools with different responsibilities. Use the local CLI primarily for installation and routine status checks, and drop into the pod (`cilium` or `cilium-dbg`) for low-level, in-cluster debugging.
Links and references
* [Cilium Documentation — CLI](https://docs.cilium.io/en/stable/gettingstarted/cli/)
* [kubectl exec reference](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#exec)