Networking & Ingress
20 articles from official documentation
Zero-Downtime Migration: From Ingress NGINX to Envoy Gateway
Migrating from Ingress NGINX to Envoy Gateway without downtime is crucial for maintaining service continuity. By leveraging weighted DNS records, you can run both systems simultaneously and control traffic flow seamlessly. This article breaks down the practical steps to achieve this migration effectively.
- →Leverage weighted DNS records to manage traffic during migration.
- →Run Ingress and HTTPRoute simultaneously to ensure zero downtime.
Mastering Ingress Request Tracing for Multi-Tenant SaaS on Kubernetes
In a multi-tenant SaaS environment, understanding request flows is crucial for maintaining performance and reliability. By implementing end-to-end ingress request tracing, you can track customer requests through your services using Trace IDs and Span IDs.
- →Implement Trace IDs to group all spans for a single customer request.
- →Use Span IDs to identify individual units of work within each service.
Building a Cloud Native Platform: Kairos, k0rdent, and bindy in Action
Creating a cloud native platform from scratch can be daunting. With Kairos, you get an immutable Linux distribution that boots from OCI images, ensuring consistency. Dive into how k0rdent and bindy enhance your Kubernetes management and DNS operations.
- →Utilize Kairos for immutable, reproducible node configurations using OCI images.
- →Define node behavior and configurations in versioned YAML through FluxCD.
Mastering EKS Container Network Observability for Inter-AZ Traffic
Understanding inter-AZ and NAT gateway traffic is crucial for optimizing your Kubernetes workloads. With EKS Container Network Observability, you gain pod-level insights into network traffic, enabling better performance tuning and troubleshooting. Dive into how to leverage this powerful feature effectively.
- →Leverage the Network Flow Monitor Agent to gain pod-level insights into network traffic.
- →Use the `trafficDistribution` field to control how traffic is routed to service endpoints.
Streamline Your Hybrid Kubernetes Networking with EKS Hybrid Nodes Gateway
Hybrid cloud environments are complex, but the Amazon EKS Hybrid Nodes gateway simplifies networking between on-premises and cloud resources. By leveraging Cilium's VXLAN Tunnel Endpoint feature, it creates seamless connections that keep your applications running smoothly.
- →Utilize the Cilium VXLAN Tunnel Endpoint feature for seamless hybrid networking.
- →Configure the `autoModeConfig` parameter to enable EKS Auto Mode.
Migrating 60+ Resources from Ingress NGINX to Higress in 30 Minutes with AI
Ready to ditch Ingress NGINX? Discover how an AI agent can streamline your migration to Higress, a cloud-native API gateway. With features like zero-downtime reliability and advanced caching, you can transition seamlessly and efficiently.
- →Utilize an AI agent to audit your existing cluster for efficient migration.
- →Generate high-performance WebAssembly (WASM) plugins to replicate existing NGINX logic.
Mastering DNS for Kubernetes Services and Pods
DNS is crucial for service discovery in Kubernetes, allowing Pods to communicate seamlessly. Understanding how Kubernetes manages DNS records can save you from frustrating connectivity issues in production environments.
- →Understand how Kubernetes creates DNS records for Services and Pods to facilitate service discovery.
- →Use A and AAAA records for normal Services to manage IP addressing effectively.
Gateway API v1.5: Stabilizing Your Kubernetes Traffic Management
Gateway API v1.5 is a game-changer for Kubernetes traffic management, moving key features to stable status. With the introduction of ListenerSets and TLSRoutes, you can streamline your routing configurations significantly. Dive in to understand how these enhancements can simplify your deployments.
- →Utilize ListenerSets to define and merge listeners independently for better traffic management.
- →Implement TLSRoutes to route requests based on SNI during the TLS handshake.
Mastering Kubernetes Services: The Key to Network Application Exposure
Kubernetes Services are essential for exposing your applications running in Pods. With the right configuration, you can seamlessly manage traffic routing and access. Dive into how to set up a Service and avoid common pitfalls.
- →Understand the role of Services in exposing Pods over the network.
- →Configure `targetPort` correctly to ensure traffic reaches the right container port.
Mastering Ingress in Kubernetes: Routing Traffic Like a Pro
Ingress is your gateway to managing HTTP and HTTPS traffic in Kubernetes. With precise routing rules, you can control how external requests reach your services. Understanding its configuration is crucial for a smooth production environment.
- →Define routing rules in the `spec` section of the Ingress resource.
- →Set `defaultBackend` to handle unmatched requests effectively.
Mastering Kubernetes Network Policies: Control Your Pod Traffic
Network Policies are crucial for securing traffic flow in your Kubernetes cluster. They allow you to define specific rules for both ingress and egress traffic, ensuring only authorized connections are made. Dive into how to implement these policies effectively in production.
- →Define ingress and egress rules to control traffic flow effectively.
- →Use podSelector to target specific Pods for your policies.
Mastering Networking Challenges with Amazon EKS Auto Mode
Tired of wrestling with complex networking setups in Kubernetes? Amazon EKS Auto Mode automates infrastructure provisioning, including networking components like the VPC CNI and load balancers, making your life easier. Dive into how this can streamline your enterprise deployments.
- →Automate infrastructure provisioning with Amazon EKS Auto Mode for streamlined networking.
- →Utilize the VPC CNI for optimal pod performance and simplified troubleshooting.
Migrating from ingress-nginx to Envoy Gateway: A Practical Guide
Ready to level up your Kubernetes ingress? Migrating to Envoy Gateway can streamline your traffic management. Pay special attention to the externalTrafficPolicy setting to avoid connection failures during health checks.
- →Configure externalTrafficPolicy to Cluster to avoid health check failures.
- →Use a reserved loadBalancerIP for consistent traffic routing.
Kubernetes v1.36: Key Changes You Need to Know
Kubernetes v1.36 is on the horizon, bringing significant changes that could impact your deployments. Notably, the deprecation of the externalIPs field means you’ll need to rethink how you route external traffic. Dive in to understand what’s changing and how to prepare.
- →Understand the deprecation policy to manage API changes effectively.
- →Prepare for the removal of the externalIPs field by exploring alternative routing options.
Migrating to Gateway API: Ingress2Gateway 1.0 Unleashed
Ingress2Gateway 1.0 is your ticket to a smoother transition from Ingress to Gateway API. It translates Ingress resources while ensuring behavioral equivalence, making your migration less daunting.
- →Install Ingress2Gateway using 'go install' or 'brew install'.
- →Translate Ingress resources with 'ingress2gateway print --input-file my-manifest.yaml'.
Five Ingress-NGINX Behaviors That Could Surprise You
Before you migrate to Ingress-NGINX, you need to understand its quirks. For instance, regex matches are prefix-based and case insensitive, which can lead to unexpected routing behavior. This article dives into what you must know to avoid pitfalls.
- →Understand that regex matches in Ingress-NGINX are prefix-based and case insensitive.
- →Use the annotation `nginx.ingress.kubernetes.io/use-regex: "true"` to enable regex matching.
Mastering API Governance in Kubernetes: What You Need to Know
API governance is crucial for maintaining stability and fostering innovation in Kubernetes APIs. Understanding the Kubernetes Enhancement Proposal (KEP) process is key to navigating changes effectively. Dive in to learn how to leverage these guidelines for your projects.
- →Understand API governance to maintain stability in Kubernetes APIs.
- →Utilize the KEP process for proposing and reviewing API enhancements.
Ingress NGINX: The Urgent Migration You Can't Ignore
Ingress NGINX is critical infrastructure for many cloud-native environments, but it's on the chopping block. By March 2026, it will be retired, leaving your deployments vulnerable. You need to check your clusters now to avoid potential compromises.
- →Run `kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx` to check your cluster's reliance on Ingress NGINX.
- →Plan your migration to alternatives like the Gateway API before Ingress NGINX is retired in March 2026.
Experimenting with Gateway API in Kubernetes: A Hands-On Guide
Unlock the power of traffic management in Kubernetes with the Gateway API. Learn how to set up a local cluster using kind and deploy a Gateway to route traffic effectively.
- →Create a local Kubernetes cluster using kind with 'kind create cluster'.
- →Deploy the cloud-provider-kind component for LoadBalancer Services.
Mastering Uniform API Server Access with clientcmd
Unlock seamless access to your Kubernetes API server with clientcmd. This powerful library simplifies handling kubeconfig files and command line arguments, ensuring you can interact with your clusters effortlessly. Dive into the specifics of how it works and what you need to watch out for in production.
- →Understand the role of KUBECONFIG for combining multiple kubeconfig files.
- →Utilize clientcmd to manage command line arguments effectively.
Unified observability — logs, uptime monitoring, and on-call in one place. Used by 50,000+ engineering teams to ship faster and sleep better.
Try Better Stack free →Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.