Linkerd Traffic Split

Prerequisites

In this lab we’ll use two docker images (oktano/sample-pizza-server-app:v2, oktano/sample-pizza-client-app:v1). Pizza client generates traffic on pizza server. Pizza server takes two environment variables so we can adjust success rate and latency of it. For initial state set success rate to 10 (which means 100%) and latency to 100ms.

You can run commands below to get to initial state.

Wait for a little bit and verify that your deployment’s success rate is 100%.

Lets deploy our ‘newer version’ of pizza-server. We’ll use same image with different success rate and shift some portion of traffic to it. Deploy and expose ‘v3’ with command down below. You can set success rate and max sleep duration to whatever you want.

After that linkerd will slowly start to shift traffic to pizza-server-v3 service. You can see it in dashboard. Check the RPS values.

pizza-server-v2 deployment’s success rate is still 100%. Because it is a seperate deployment from pizza-server-v3. To see overall success rate from pizza-client deployment’s point of view run:

Cleanup

To remove everything from this lab use kubectl delete ns pizza-app command.

Related posts:

Some people are having difficulties in distinguishing a horse from a pony and still believe that a pony will grow, like a grown up. PRSC Enterprises China F&B importer since 1997 Bianca Zhang