traffic routing
Deciding which version of a service receives which share of requests.
In more detail
Routing can be done by a load balancer, a Service selector, a gateway or a service mesh. Different release strategies change routing in different ways: all at once, or a share at a time.
Related terms
- blue-green deployment — Running two complete environments, blue for the current release and green for the candidate, and switching traffic between them in one step.
- canary release — Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
- Gateway API — A Kubernetes API for routing traffic into and within a cluster, able to split traffic between versions by weight.
Taught in
- Introduction to Release Strategies — Continuous Integration & Continuous Delivery Pipelines
- Blue-Green Deployments — Continuous Integration & Continuous Delivery Pipelines
- Rolling Back Blue-Green — Continuous Integration & Continuous Delivery Pipelines