Having the flexibility to release software changes to a private and small subset of users to verify and test changes can have a huge positive impact on the deployment process.
This happens has a number of names and approaches, such as Blue Green Deployments and Canary Releases. The aim of is to enable changes to be rolled out more frequently, with higher confidence.
In this scenario, you will learn how to perform blue-green and canary releases with Envoy Proxy. The scenario will explain:
Access private deployments via HTTP Headers.
Shift 20% of traffic to a new release to test against production traffic.
Roll out 100% of traffic to a new release.
In this scenario you learned how to perform blue green and canary releases with Envoy Proxy. The scenario explained:
Accessing private deployments via HTTP Headers.
Shifting 20% of traffic to a new release to test against production traffic.
Rolling out 100% of traffic to a new release.
Implementing Blue / Green rollouts
Step 1 - Envoy Base Configuration
A base Envoy configuration has been defined in the file
Open the file
envoy.yaml and review the configuration.
Question: How many routes have been defined within the configuration?
Question: How many clusters have been defined within the configuration?
The next steps will extend this base configuration to support a private release, following by sending a percentage of production traffic to a new version.