Types of intercepts
Personal intercepts allow you to be selective and intercept only some of the traffic to a service while not interfering with the rest of the traffic. This allows you to share a cluster with others on your team without interfering with their work.
In the illustration above, Orange requests are being made by Developer 2 on their laptop and the green are made by a teammate, Developer 1, on a different laptop.
Each developer can intercept the Orders service for their requests only, while sharing the rest of the development environment.
Creating and using personal intercepts
Creating the intercept: Intercept your service from your CLI:
Personal-Intercept=126a72c7-be8b-4329-af64-768e207a184bas the header for the sake of the example, but you can use any
key=valuepair you want, or
--http-match=autoto have it choose something automatically.
Using the intercept: Send requests to your service by passing the HTTP header:
Using the intercept: Send requests to your service without the HTTP header:
Requests without the header will be sent to the version of your service that is running in the cluster. This enables you to share the cluster with a team!