Personal intercept

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.

Creating and using personal intercepts

1. Creating the intercept: Intercept your service from your CLI:

   We're using Personal-Intercept=126a72c7-be8b-4329-af64-768e207a184b as the header for the sake of the example, but you can use any key=value pair you want, or --http-match=auto to have it choose something automatically.

   Make sure your current kubect context points to the target cluster. If your service is running in a different namespace than your current active context, use or change the --namespace flag.

2. Using the intercept: Send requests to your service by passing the HTTP header:

   Need a browser extension to modify or remove an HTTP-request-headers?

   Chrome Firefox

3. 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!