Skip to content

Latest commit

 

History

History

oci-devops-deploy-with-blue-green-model

README.md

Sample illustration of OCI Devops deployment pipeline with BLUE-GREEN deployment strategies using Oracle Container Engine for Kubernetes (OKE).

Objective

  • Create OCI Devops build pipeline.
  • Build a sample python application.
  • Push the artifact to OCI Container and OCI Artifact repo.
  • Use OCI Deployment pipeline with BLUE/GREEN Deployment strategies.
  • Validate deployment and manual role back.

Specific instructions to download only this sample.

    $ git init oci-devops-deploy-with-blue-green-model
    $ cd oci-devops-deploy-with-blue-green-model
    $ git remote add origin https://github.com/oracle-devrel/oci-devops-examples
    $ git config core.sparsecheckout true
    $ echo "oci-deployment-examples/oci-devops-deploy-with-blue-green-model/*">>.git/info/sparse-checkout
    $ git pull --depth=1 origin main

Procedure

  • Create an artifact as type Kubernetes manifest.Ensure to add your artifact repo path and version as ${BUILDRUN_HASH} .

  • Accordingly select the code repo /connection type /repo name.

If you are using a code repo other than OCI code repo ,ensure to set an external connection - https://docs.oracle.com/en-us/iaas/Content/devops/using/create_connection.htm

  • Add an Deliver artifact stage to the build pipeline.

  • Select the two artifacts created.

  • Associate the build stage output artifact names .

outputArtifacts:
  - name: oke_app_base
    type: DOCKER_IMAGE
    # this location tag doesn't effect the tag used to deliver the container image
    # to the Container Registry
    location: oke_app_base:latest

  - name: oke_deploy_manifest
    type: BINARY
    # this location tag doesn't effect the tag used to deliver the container image
    # to the Container Registry
    location: ${OCI_PRIMARY_SOURCE_DIR}/oci-oke-deployment.yaml

  • Add a stage as Blue/Green Strategy.

  • Select the Deployment type as OKE and select the environment created.

  • Associate the oke environment created.

  • Select Namespace A as ns-green and Namespace B as ns-blue.(These are names for test ,you may use other names accordingly)

  • Select the Kubernetes Artifacts.

  • Fill the ingress name as sample-oke-bg-app-ing .It’s the sample ingress name declared via deployment manifest.

  • As its a demo keep the Validation controls as None or you may connect with a function to validate the deployment.

  • Enable the Approval controls and add 1 as the number of approvers.

  • Click add to add the stages.

  • Switch back to Build pipeline and add a Trigger Deployment stage. Select the deployment pipeline and associate. Ensure to check the Send build pipelines Parameters option.

  • In order to run the blue green we should install Nginx Ingress Controller to our OKE cluster.
  • Launch OCI Cloud shell to enable the OKE access.
  • Follow the instruction via Access Cluster tab for the OKE cluster.

  • Validate the Kubernetes access using kubectl get nodes & kubectl config view.

kubectl create clusterrolebinding oke_cluster_role_<username> --clusterrole=cluster-admin --user=ocid1.user.oc1..xxx

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.2/deploy/static/provider/cloud/deploy.yaml
  • Create and save the file cloud-generic.yaml containing the following code to define the ingress-nginx ingress controller service as a load balancer service.
kind: Service
apiVersion: v1
metadata:
  name: ingress-nginx
  namespace: ingress-nginx
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
spec:
  type: LoadBalancer
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
  ports:
    - name: http
      port: 80
      targetPort: http
    - name: https
      port: 443
      targetPort: https
  • Using the file you just saved, create the ingress-nginx ingress controller service by running the following command.
kubectl apply -f cloud-generic.yaml
  • You may follow the procedure to create a TLS certificate for nginx.
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj "/CN=nginxsvc/O=nginxsvc"
kubectl create secret tls tls-secret --key tls.key --cert tls.crt

  • You may skip the sample application example in the procedure.

  • Validate the installation.

kubectl get svc -n ingress-nginx
  • The EXTERNAL-IP for the ingress-nginx ingress controller service is shown as pending until the load balancer has been fully created in Oracle Cloud Infrastructure. Repeat the kubectl get svc command until an EXTERNAL-IP is shown for the ingress-nginx ingress controller service.

  • Create two new namespaces for the deployment.
kubectl create ns ns-blue;kubectl create ns  ns-green
  • Go back to build pipeline and do click Start manual run.

  • Wait until all the build stages completed.

  • Switch to the deployment pipeline and click on the deployment which is in progress.

  • The pipeline will be pending for Approval stage.
  • Validate the first deployment at this stage. You should see a valid deployments at namespace ns-green.
for i in ns-green ns-blue ; do echo "-- NS:$i --";kubectl get po,ing -n $i; done

  • Click on the 3 dots and validate the Control:Approval stage.

  • Wait for all the steps to complete.

  • Validate the deployment using the Ingress Address.
curl -k http://<Ingress Address>
  • Edit the source code - main.py and change the version to 0.1 and run the build pipeline again to test a new deployment scenario.
from typing import Optional

from fastapi import FastAPI

import os

app = FastAPI()

@app.get("/")
def read_root():
    version="0.0"
    namespace = os.getenv('POD_NAMESPACE', default = 'ns-red')
    return {"Message": "with Love from OCI Devops ","Version":version,"Namespace":namespace}

Let's Test

  • Go back to build pipeline and do click Start manual run.

  • Wait untill all the build stages completed.

  • Switch to the deployment pipeline and click on the deployment which is in progress.

  • The pipeline will be pending for Approval stage.
  • Validate the first deployment at this stage. You should see a valid deployments at namespace ns-blue too.
for i in ns-green ns-blue ; do echo "-- NS:$i --";kubectl get po,ing -n $i; done

  • Validate the deployment using the Ingress Address.
curl -k http://<Ingress Address>

Output :

{"Message":"with Love from OCI Devops ","Version":"0.1","Namespace":"ns-blue"}

  • You can continue other re-run from build pipeline and validate the switch between environment.

  • Let us now try a Manul rollback.

  • Use the 3 dots at the stage Traffic Shift stage and select Manual Rollback.

  • Select a previously successful deployment.

  • Close the select deployment page and click Rollback Stage option.

  • Wait for stage to complete .

  • Validate the deployment using the Ingress Address.
curl -k http://<Ingress Address>

Output :

{"Message":"with Love from OCI Devops ","Version":"0.0","Namespace":"ns-green"}

Note : Re-Run of deployment pipeline with OKE Blue-Green stage is not supported for now.

Read more

Contributors

  • Author : Rahul M R.
  • Collaborators : NA
  • Last release : March 2022

Back to examples.