liveBook · Manning

Path-based routing

As explained in Kubernetes for Developers

Path-based routing directs requests to different backends according to the URI path.

Path-based routing directs HTTP requests to different backend services according to the URI path. In Kubernetes, an Ingress provides this layer-7 routing while allowing multiple services to share one external IP and domain. section 7.2

Splitting a growing application

Move a CPU-intensive endpoint into its own Service, then route its existing URL path to that Service. The workload can scale separately without changing public-facing URLs. section 7.2

How Kubernetes for Developers covers it

How deep it goes
Explains Ingress rules, backend Services, and deployment inspection, but stops short of TLS configuration details.
Examples
Uses root and /robohash paths mapped to timeserver-internal and robohash-internal Services.
What it assumes
Assumes familiarity with Kubernetes Services and Pods while showing the required NodePort configuration for Ingress backends.
What you can do after
Configure Kubernetes Ingress rules that map URI paths to backend Services and inspect the resulting address and health.
How it connects
Connects Ingress with HTTP load balancing, Services, URI paths, host-based routing, and independent application scaling.
Cover of Kubernetes for Developers
liveBookmanning.com
Read Kubernetes for Developers on liveBook Get the book at manning.com

Also explained in

Compare how 2 books explain path-based routing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kubernetes for Developers. The section links point to the parts of the book it draws on.