Cilium
Saves to local browser storage. Followed topics appear on the homepage and refresh on each visit.Also known as cilium cni·cilium service mesh·cilium hubble·cilium tetragon·cilium project
Latest from across the web
External coverage we have crawled and indexed for this topic.
When Kubeflow meets Cilium: Debugging 60% idle GPUs in Kubernetes
The symptom that made no sense The first time we saw it, we didn’t trust the dashboard. A distributed training job was scheduled and healthy — every pod was running, no crashes, no OOMKills…
The Kubernetes integration tax: Prometheus, Cilium and production reality
I still remember the first time we lost sleep over something that wasn’t a bug. It was a Tuesday. Grafana dashboards showed blank panels for Cilium network metrics. Hubble was working fine — DNS…
Navigating the ingress-nginx archival: why now is the time to move to Cilium
This Member Blog was originally published on the Isovalent blog and is republished here with permission. If you’re running Kubernetes, there’s a good chance you rely on ingress-nginx to route external
Videos
From the channels we track
People also ask
Common questions on Cilium, surfaced from across the indexed web.
Why Choose Cilium’s Gateway API Implementation?
Cilium’s Gateway API implementation isn’t just a replacement; it’s an upgrade that brings a host of benefits, from enhanced traffic control to streamlined operations. Advanced traffic management: Native support for header-based routing, traffic splitting, and cross-namespace routes. Unified traffic management (GAMMA): Leverage a single, consistent API (Gateway API) to manage both external (north-south) ingress traffic and internal (east-west) service mesh traffic, simplifying operations and policy enforcement. Role separation: Decouple infrastructure from application routing for better secur
Navigating the ingress-nginx archival: why now is the time to move to CiliumWhat Are Your Options?
With ingress-nginx entering retirement, platform teams face a choice: keep a critical control-plane component without upstream maintenance, or move to an actively supported alternative. The Kubernetes community has aligned on the Gateway API as the long-term standard for traffic management. That direction shapes your two primary migration paths: Move to another ingress controller (such as Cilium Ingress, Traefik, or HAProxy Ingress). Adopt the Kubernetes Gateway API, the next-generation standard for ingress and traffic management, using a controller like Cilium Gateway API. Cilium offers both
Navigating the ingress-nginx archival: why now is the time to move to CiliumWhat Are the Key Features Over Ingress?
While Ingress has served us well, its design inherently limits advanced traffic management. The Gateway API, especially with Cilium’s implementation, unlocks a new level of control and flexibility. This table highlights some key areas where Gateway API goes beyond what traditional Ingress can offer, providing more robust and granular control over your traffic flows.
Navigating the ingress-nginx archival: why now is the time to move to CiliumWhich Path Should You Take First?
Most teams start with Cilium Ingress to remove the maintenance risk immediately, then move to the Gateway API as their routing and organizational needs evolve. If your platform already separates infrastructure and application teams, Gateway API will feel natural from the start. If your environment is smaller or less complex, Cilium Ingress offers the fastest path to replace ingress-nginx with minimal change. A practical migration plan: Document current behaviour: Capture hosts, paths, TLS, health checks, and any NGINX annotations. Select a target: Choose Cilium Ingress for quick replacement,
Navigating the ingress-nginx archival: why now is the time to move to Cilium