Skip to content

Commit ad3745d

Browse files
author
Gino Mempin
committed
docs: Add info on Blue/Green type deployment
1 parent 0965cea commit ad3745d

File tree

3 files changed

+13
-0
lines changed

3 files changed

+13
-0
lines changed

README.md

+13
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ These are my notes from tutorials on using K8s to deploy applications.
2020
* [Deployments](#deployments)
2121
* [RollingUpdate](#rollingupdate)
2222
* [Canary](#canary)
23+
* [Blue/Green](#bluegreen)
2324
* [Troubleshooting](#troubleshooting)
2425
* [Sample Application](#sample-application)
2526
* [References](#references)
@@ -186,6 +187,18 @@ Note that secrets can also be declaratively defined in a YAML file, **BUT** any
186187
187188
![Canary Deployment](./docs/deployment.canary.png)
188189
190+
### Blue/Green
191+
192+
First, setup 2 identical environments: 1 for public use (**blue**) and 1 for internal use (**green**).
193+
194+
![Blue/Green Deployment 1](./docs/deployment.blue-green.1.png)
195+
196+
Next, once all the tests on the **green** deployment passes, switch the public service to serve the **green** deployment.
197+
198+
![Blue/Green Deployment 2](./docs/deployment.blue-green.2.png)
199+
200+
Finally, delete the old **blue** deployment.
201+
189202
### Best Practices
190203
191204
See [Best Practices when using Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#best-practices).

docs/deployment.blue-green.1.png

259 KB
Loading

docs/deployment.blue-green.2.png

258 KB
Loading

0 commit comments

Comments
 (0)