⌘K

The Gateway API , formerly known as the Services API and before that Ingress V2, was first discussed in detail — and in-person — at Kubecon 2019 in San Diego. There were already many well-known and well-documented limitations of Ingress and Kubernetes networking APIs. The Gateway API was intended as a redo of these APIs, built on the lessons from Services, Ingress and the service mesh community.

#kubernetes #networking #contributed #sponsored

thenewstack.io

Unifying Kubernetes Service Networking (Again) with the Gateway API

Thanks to well-defined conformance and a layered API model, the Gateway API already shows a lot of promise and a long road ahead. There were already many well-known and well-documented limitations of Ingress and Kubernetes networking APIs. The Gateway API was intended as a redo of these APIs, built on the lessons from Services, Ingress and the service mesh community.

1.10 GEEK