Blue/Green Deployment
Users can perform blue/green deployments using Ingress or Service.
Adding a blue/green deployment means creating a new K8S Ingress or K8S Service so that the two Helm releases can be swapped.
Only two Helm releases that have the same project, cluster, namespace, release type, chart name, chart version, development classification can be grouped.
Starting Blue/Green Deployment
To start using blue/green deployment, follow these steps.
- On the Main page, click the Project card. You will be taken to the Project Dashboard page.
- Click the Build/Deploy > Kubernetes Deploy menu in the left menu. You will be taken to the Kubernetes Deploy page.Item
Explanation Name Displays the blue/green deployment name. Click to view detailed information. Cluster/Namespace Displays the deployed cluster/namespace. (operation) Displays information about the currently deployed Helm release. (operational standby) Shows the Helm release that will be the next version in operation. Using blue/green switching, the standby switches to active. Delete Delete the current item. Table. Kubernetes deployment screen Blue/Green deployment card items - Click the name of the Blue/Green deployment you want to start from the deployment list on the Kubernetes deployment page. You will be taken to the Deployment details page.
Add blue/green deployment
To add a blue/green deployment, follow these steps.
- Click the Project card on the Main page. You will be taken to the Project Dashboard page.
- Click the Build/Deploy > Kubernetes Deploy menu in the left menu. You will be taken to the Kubernetes Deploy page.
- Click the Add Blue/Green Deployment button at the top right of the Kubernetes deployment page. The Add Blue/Green Deployment popup opens.
- Add Blue/Green deployment After entering the information in the popup window, click the Save button to complete adding the Blue/Green deployment.Item
Explanation Category Select Development, Operations - The actions each role can perform differ depending on the Development or Operations classification.(Table. Role-based permissions within the project (2))
Blue/Green deployment name Enter the deployment name. Operation Release and Jenkins Job selection - Release name: Select the name of the currently running Helm release from the list.
- Jenkins Job: Select the Jenkins Job from the list to build/deploy the selected Helm release.
Standby Release and Jenkins Job selection - Release name: Select the name of the Helm release to be applied to production in the next version from the list.
- Jenkins Job: Select the Jenkins Job from the list to build/deploy the selected Helm release.
K8S cluster/namespace Displays the K8S cluster/namespace where the Helm release is installed. Type classification Select whether to use Ingress or Service to perform a blue/green switch. New classification Choose whether to create a new Ingress or Service, or use an existing one. Name Enter name - New: Enter the name of an Ingress or Service.
- Existing: Select an already created Ingress or Service from the list.
Service (Operation) Select the Kubernetes Service related to the currently running Helm release from the list. Service (Operational Standby) Select the Kubernetes Service related to the Helm release that will be applied to operations in the next version from the list. Rules Enter the information to be used for Ingress. Table. Ingress type input items when adding blue/green deploymentItem Explanation type Select the type of Kubernetes Service from the list ClusterIPNodePortLoadBalancer
Deployment (Production) Select the Kubernetes Deployment related to the currently running Helm release from the list. Deployment (Operational standby) Select the Kubernetes Deployment related to the Helm release that will be operated in the next version from the list. Ports Enter the information to be used by the Service. Table. Service type input items when adding Blue/Green deployment
Replace Blue/Green
To replace the blue/green, follow these steps.
- Click the Blue/Green Switch button on the Deployment Details page. The Blue/Green Switch popup opens.
- In the Blue/Green replacement popup, click the Confirm button to complete the Blue/Green replacement.
- The Helm releases for production and staging are being swapped.
- A replacement record will be added.
Check the yaml of Ingress or Service for blue/green deployment
To check the yaml of the Ingress or Service used in blue/green, follow these steps.
- On the Deployment Details page, click the view icon for Ingress YAML or Service YAML. The Ingress YAML or Service YAML popup window opens.
- Ingress YAML or Service YAML popup window, review the contents and click the Confirm button to exit.
Managing Jenkins Jobs for Blue/Green Deployments
Jenkins Job View Log
To view the Jenkins Job log, follow these steps.
- On the Deployment Details page, click the Log button in the Jenkins Job entry for the desired release. The Pipeline Log popup window opens.
- Pipeline Log After confirming the log in the popup window, click the Confirm button.
Running a Jenkins Job
To run a Jenkins job, follow these steps.
- On the Deployment Details page, click the Run button in the Jenkins Job entry for the desired release. The Enter Pipeline Execution Parameters popup will open.
- Pipeline Execution Parameter Input In the popup window, enter or select each item, then click the Confirm button to complete the Jenkins Job execution.
Modify blue/green deployment
To modify a blue/green deployment, follow these steps.
- Deployment Details page, click the Edit button. The Blue/Green Deployment Edit popup window opens.
- Blue/Green Deployment Edit In the popup window, modify the desired items and click the Save button to complete the edit.
Delete blue/green deployment
To delete a blue/green deployment, follow these steps.
- Deployment Details page, click the Delete button. The Blue/Green Deployment Delete popup opens.
- Blue/Green deployment deletion in the popup window, select whether to execute the Ingress/Service deletion command, and click the Confirm button to complete the deletion.
Execute Ingress/Service deletion command
- Selection: The Ingress or Service used for blue/green deployment is actually deleted from the cluster.
- Unselected: Ingress or Service used for blue/green deployment is not deleted and remains in the cluster.