All Aboard! Kubernetes Routes now available for all destinations, North/South and East/West

Whether it's northbound traffic using Ingress or eastbound traffic through the Service Mesh, either way, your ultimate goal as a Kubernetes platform engineer is direct traffic along Routes to cluster services.

There's a lot of similarity in what's needed to route that traffic to the appropriate Kubernetes workload acting as service backend, no matter if it is traffic from outside the cluster making use of a Gateway API compliant gateway or if it is traffic between services inside the cluster making use of a service mesh solution. It turns out, that the appropriately named family of Route objects introduced in the Kubernetes Gateway API design is able to express the traffic routing rules for both Ingress and Service Mesh traffic, for both north/south bound traffic into/out of the cluster as well as east/west traffic flowing between services in the cluster.

Climb aboard this train-themed talk, and learn the fundamentals of how the GAMMA Project builds on The Kubernetes Gateway API to extend Routes so that can be attached to Kubernetes services when Gateway API compliant service meshes are in use in the cluster.