Watch the video to see the difference between Gateway API and Ingress based on 4 dimensions: multitenancy, specifications, advanced traffic management, and extensibility.
The Ingress resource is officially frozen. New Ingress developments are made in Kubernetes Gateway API. Gateway API CRDs standardize the specifications for configuring Ingress rules.
Instead of kind Ingress, Gateway API CRDs include GatewayClass, Gateway, and *Route (HTTP, TCP, etc.) resources. They are also portable across a variety of Ingress controller and service mesh implementations.
In the video, you’ll see a direct comparison between Ingress resource and Gateway API based on 4 dimensions. You’ll see that Gateway API CRDs offer broader capabilities and solve the drawbacks with Ingress.
▬▬▬▬▬ Timestamp ▬▬▬▬▬▬
00:00 Introduction
00:10 Agenda
00:30 Introduction to Kubernetes Ingress
01:00 Introduction to Gateway API
02:15 Dimensions of comparison
02:30 Multitenancy
05:12 Specification
09:00 Advance traffic management
11:15 Extensibility
13:00 Example of ReferenceGrant
14:00 Summary
▬▬▬▬▬ Additional resources ▬▬▬▬▬▬
➡️ Blog: Ingress vs Gateway API: imesh.ai/blog/kubernetes-gate...
➡️ Introduction to Kubernetes Gateway API: • Getting Started With K...
➡️ Kubernetes Ingress vs Istio Ingress Gateway: • Kubernetes ingress vs ...
➡️ Learn Istio service mesh from scratch in 3 hrs: www.udemy.com/course/istio-se...
➡️ Looking for Istio at scale, without any of its operational complexities? Check this out: imesh.ai/managed-istio.html
▬▬▬▬▬ About IMESH ▬▬▬▬▬▬
IMESH offers a Kubernetes-native application network and security platform to manage multi-cloud and hybrid-cloud environments. The IMESH platform is built on top of Istio service mesh and Envoy API gateway and helps cloud, platform, and security teams to make Kubernetes applications more secure, manageable, and reliable.
▬▬▬▬▬ Connect ▬▬▬▬▬▬
Website: imesh.ai/
GitHub: github.com/imesh-ai
LinkedIn: / imeshai
▬▬▬▬▬▬ Thanks ▬▬▬▬▬▬
#kubernetes #gatewayapi #ingress