Tracked topic
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 CiliumWith 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 CiliumWhile 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 CiliumMost 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… Define GatewayClass and Gateway resources : This is a simple example, but you can find more detailed examples in this tutorial blog post for Gateway API: apiVersion: gateway.networking.k8s.io/v1beta1 kind: GatewayClass metadata: name: cilium spec: controllerName: io.cilium/gateway-controller --- ap… …
… Update the ClusterIssuer: Either update the current issuer or create a new one: apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata: name: letsencrypt-prod spec: acme: preferredChain: "" privateKeySecretRef: name: letsencrypt-prod server: https://acme-v02.api.letsencrypt.org/directory solve… …
… Gateway API 1.5 is a stable release and addresses this directly. The issue is that controllers have not caught up to the spec yet. Where Gateway API goes from here Gateway API 1.5 shipped with ListenerSet, a new resource type designed to enable this separation of concerns. …
… Loading the Image into Kind bash kind load docker-image envoy-wrapper:latest --name ai-gateway-lab Part 6: Deploying the Custom Envoy Image To deploy your custom image without kgateway’s controller reverting changes, use GatewayParameters: yaml apiVersion: gateway.kgateway.dev/v1alpha1 kind: Gatewa… …
… Option 1: Move to the Gateway API As the modern replacement of Ingress, this is the recommended option for our internal users. During 2025 we moved to Cilium as our default CNI plugin, which brings built-in support for the Gateway API. …
… Inference Gateways: These utilize Gateway API standards to build efficient AI Gateways, which help with prompt management and high-intensity generative model responses. How does AI change the role of an engineer? AI is reshaping internal engineering roles. …
… This blog post explains how full migration validation was achieved in just 30 minutes by leveraging an AI agent and Higress , a cloud-native and AI-native API gateway founded by Alibaba that recently joined the CNCF Sandbox. …
… The UI uses streaming events to send trace context such as error logs and key-value tags to the backend gateway. …
… This enables: Automated reconciliation without manual kubectl use Full auditability via Git history and sync status Easy rollbacks using standard Git workflows The Argo CD Application CRD below shows how a microservice is configured for automated sync with self-healing and pruning enabled: Argo CD … …
To show you the most relevant results, we’ve omitted some entries very similar to those already shown. Repeat the search with the omitted results included.