Kubernetes Ingress vs Gateway API
🔹 What is Ingress?
- Ingress is the traditional way to expose HTTP/HTTPS services in Kubernetes.
- It uses Ingress Controllers (like NGINX, Traefik, HAProxy) to route traffic into the cluster.
- You define rules (host/path → service) in an Ingress resource.
✅ Pros: Simple, widely supported, good for basic routing.
❌ Cons: Limited features (TLS termination, path/host routing only), different controllers add their own non-standard annotations.
🔹 What is Gateway API?
🔅 Gateway API is a next-generation replacement for Ingress.
🔅 Provides more flexibility, consistency, and extensibility.
🔅 Designed with multiple personas in mind:
- Infrastructure teams manage Gateways.
- Application developers define Routes.
🔅 Supports richer traffic management (weight-based routing, retries, timeouts, header matching, etc.).
Key Resources in Gateway API:
🪝 GatewayClass – Defines the type of gateway (like IngressClass).
🪝 Gateway – The actual instance (like a load balancer).
🪝 HTTPRoute – Routes HTTP traffic to services.
🪝 TCPRoute/UDPRoute – Non-HTTP traffic.
🪝 ReferenceGrant – Lets apps in one namespace reference resources in another.
✅ Pros: Standardized, portable across implementations, supports advanced features (blue/green, canary, header-based routing).
❌ Cons: Newer, learning curve is bigger.
🔹 Ingress vs Gateway API — The Core Difference
- Ingress = Simple, legacy, limited but widely available.
- Gateway API = Modern, modular, scalable, with first-class support for advanced traffic control...
Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been released and with it comes brand new Cloud Management Platform – VCF Automation (VCFA) which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Comments
Post a Comment