Complete CI/CD Pipeline Setup on Oracle Cloud Infrastructure (OCI) with Oracle Kubernetes Engine (OKE) – Blue/Green Deployment Strategy

 

Building a modern CI/CD pipeline is essential for delivering applications faster, safer, and with minimal downtime. In this blog, I’ll walk you through a complete end-to-end implementation of a CI/CD pipeline in OCI DevOps, integrating GitHub, Container Registry, OKE, and implementing a Blue/Green Deployment strategy.

 

 

 

This setup ensures:

• Automated build and deployment
• Zero-downtime releases
• Easy rollback mechanism
• Secure secret management

 

Let’s dive in.

Architecture Overview

We will configure:

• GitHub repository (source code)
• OCI Vault & Secrets
• OCI Container Registry
• OCI DevOps Project
• Build Pipeline
• Deployment Pipeline
• OKE Cluster
• NGINX Ingress Controller
• Blue/Green namespaces (ns-blue & ns-green)

 

Step 1: Secure GitHub Token in OCI Vault

Instead of hardcoding secrets:

1. Create a Vault
2. Create a Master Encryption Key
3. Store the GitHub PAT token as a Secret
4. Reference the secret in DevOps pipeline

This ensures enterprise-grade security for repository mirroring.

After  a vault is created, create the encryption key inside the vault

Now refer the key to the secrets

 

Secret contents is the PAT(Personal Access token) for the github. 

 

Step 2: Create an OKE Cluster

Create an OKE cluster from OCI Console.

After creation, access it from Cloud Shell:

kubectl get nodes

Your Kubernetes cluster is now ready for deployments.

3 worker nodes are up and running

 

Step 3: Create Container & Artifact Registry

• Create Container Registry → Stores Docker images
• Create Artifact Registry → Stores Kubernetes manifest files (YAML)

These artifacts will be referenced inside the pipeline.

 

Container registry:-

Artifact Registry

 

Step 4: Mirror GitHub Repository in OCI DevOps

Inside DevOps Project:

1. Click Mirror Repository
2. Provide GitHub credentials (via Vault secret which stores the GitHub PAT)
3. Wait for sync

After a few minutes, your source code will reflect in OCI.

 

 

 

 

Once it is created, we will be able to see the repositories present inside my github

 

 

 

 

After few minutes, the files will be displayed

 

 

Create the artifcats inside the devops which will store the container images and OKE manifest files

 

 

 

 

 Click on add

 

 Create the OKE manifest artifacts (choose the artifact registry created earlier)

 

 

 

Step 5: Create Build Pipeline

Important: Ensure build_spec.yaml is present in the root of the repository.

Build Pipeline Flow:

• Fetch Source Code
• Build Docker Image
• Push Image to Container Registry
• Export Image Artifact
• Trigger Deployment Pipeline

 

 

Add the next stage to deliver the artifacts for next stage

 

Click on +

 

 

 

 

Step 6: Create OKE Deployment Environment

Create an environment pointing to:

• Your OKE Cluster
• Target Namespace
• Kubernetes Manifest (oci-oke-deployment.yaml)

 

 

Step 7: Create Deployment Pipeline

 

 

 

 

 

 

Click on next

 

 

Select the environment created earlier

 

 

 

 

 

 

 

Add the trigger deployment under the build pipeline

 

 

 

 

 

Conclusion (End of Part 1)

By completing the steps above, we have successfully:

• Secured GitHub credentials using OCI Vault
• Created an OKE cluster
• Configured OCI Container & Artifact Registry
• Set up OCI DevOps Project
• Created a Build Pipeline
• Configured a Deployment Environment
• Implemented Blue/Green namespaces (ns-blue & ns-green)

At this stage, the CI/CD foundation is fully ready.

 

However, traffic is not yet exposed externally. The application is deployed inside the cluster, but we still need:

• An Ingress Controller
• Load Balancer configuration
• Traffic routing between Blue and Green
• Manual approval-based traffic shift
• Rollback mechanism

These critical production-grade components will be covered in the next blog.

---

What’s Coming in next post

In the next post-https://samappsdba.blogspot.com/2026/02/oci-devops-cicd-oke-blue-green-ingress-traffic-shift-part-2.html, we will cover:

• Setting up NGINX Ingress Controller on OKE
• Configuring LoadBalancer service
• Executing build pipeline runs
• Deploying to Green namespace
• Traffic shifting to Blue namespace
• Rollback strategy in OCI DevOps

This is where the real power of OCI DevOps Blue/Green deployment becomes visible.

 

Thanks for reading.

 

 

OCI DevOps CI/CD Pipeline with OKE Blue/Green Deployment – Part 2 (Ingress Setup, Traffic Shift & Rollback)

 In Part 1, we built the complete CI/CD foundation using:

• OCI Vault

• OCI Container & Artifact Registry

• OCI DevOps Build Pipeline

• OKE Cluster

• Blue/Green Namespaces

If you missed it, read Part 1 here:
https://samappsdba.blogspot.com/2026/02/oci-devops-cicd-pipeline-oke-blue-green-setup-part1.html

Now in Part 2, we will:

• Set up NGINX Ingress Controller

• Configure LoadBalancer

• Execute build pipeline

• Deploy to Green namespace

• Shift traffic to Blue namespace

• Perform rollback

This is where the real power of Blue/Green deployment on Oracle Cloud Infrastructure using Oracle Kubernetes Engine becomes visible

Step 8: Setup NGINX Ingress Controller on OKE

To expose applications externally, we need an Ingress Controller.

From OCI Cloud Shell, run:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.3.0/deploy/static/provider/cloud/deploy.yaml

Verify services:

kubectl get svc -n ingress-nginx

Configure Ingress Service as LoadBalancer

yaml file

kind: Service

apiVersion: v1

metadata:

  name: ingress-nginx

  namespace: ingress-nginx

spec:

  type: LoadBalancer

  selector:

    app.kubernetes.io/name: ingress-nginx

  ports:

    - name: http

      port: 80

      targetPort: http

    - name: https

      port: 443

      targetPort: https

Apply it:-

kubectl apply -f cloud-generic.yaml

Now your OKE cluster can route external traffic.

Step 9: Execute Build Pipeline

Go to OCI DevOps → Build Pipeline → Start Manual Run.

The pipeline will:

• Execute build_spec.yaml

• Build Docker image

• Push image to OCI Container Registry

• Trigger deployment pipeline

Check the deployment pipeline

Verify deployments:

NAME                                                READY   STATUS    RESTARTS   AGE

pod/sample-oke-bg-app-deployment-55db78c699-blz7r   1/1     Running   0          7m13s

pod/sample-oke-bg-app-deployment-55db78c699-d9zwh   1/1     Running   0          6m31s

pod/sample-oke-bg-app-deployment-55db78c699-fpj6h   1/1     Running   0          7m56s

 

NAME                                              CLASS    HOSTS   ADDRESS          PORTS   AGE

ingress.networking.k8s.io/sample-oke-bg-app-ing   <none>   *       129.80.114.230   80      41m

-- NS:ns-blue --

No resources found in ns-blue namespace.

Initially, traffic routes to ns-green.

Open the External IP in browser — application loads from Green namespace.

After it has been validated and passed the QA, approve it

Traffic is shifted to green namespace after successful test

Step 10: Modify Code & Deploy New Version

Commit changes to GitHub.

Within minutes:

• Code mirrors to OCI DevOps repository

• Start manual build again

• New image appears in Container Registry

• Deployment pipeline deploys to ns-blue

Now the pipeline waits for approval.

Step 11: Traffic Shift to Blue Namespace

After approval in Deployment Pipeline:

Traffic shifts from ns-green → ns-blue

Validate:

-- NS:ns-green --

NAME                                                READY   STATUS    RESTARTS   AGE

pod/sample-oke-bg-app-deployment-55db78c699-blz7r   1/1     Running   0          62m

pod/sample-oke-bg-app-deployment-55db78c699-d9zwh   1/1     Running   0          62m

pod/sample-oke-bg-app-deployment-55db78c699-fpj6h   1/1     Running   0          63m

 

NAME                                              CLASS    HOSTS   ADDRESS          PORTS   AGE

ingress.networking.k8s.io/sample-oke-bg-app-ing   <none>   *       129.80.114.230   80      97m

-- NS:ns-blue --

NAME                                                READY   STATUS    RESTARTS   AGE

pod/sample-oke-bg-app-deployment-57dd5dc988-4cvtv   1/1     Running   0          2m58s

pod/sample-oke-bg-app-deployment-57dd5dc988-hr7rt   1/1     Running   0          2m58s

pod/sample-oke-bg-app-deployment-57dd5dc988-lvp2h   1/1     Running   0          2m58s

 

NAME                                              CLASS    HOSTS   ADDRESS          PORTS   AGE

ingress.networking.k8s.io/sample-oke-bg-app-ing   <none>   *       129.80.114.230   80      51m

samsin16@cloudshell:~ (us-ashburn-1)$

 

we can see that pods are now running under blue

Ingress still uses the same External IP — but backend changes.

This ensures:

• Zero downtime

• Controlled release

• No service interruption

Step 12: Rollback (If Required)

If something goes wrong:

In Deployment Pipeline → Click Revert Traffic Shift

Traffic instantly returns to ns-green.

No rebuild required.
No downtime.
No manual intervention inside Kubernetes.

This is the beauty of OCI DevOps Blue/Green deployment

What We Achieved

By completing Part 2, we now have:

• Full CI/CD automation

• Kubernetes ingress routing

• Blue/Green traffic switching

• Approval-based production release

• Instant rollback capability

All running natively on Oracle Cloud Infrastructure.

---

Conclusion

With OCI DevOps and OKE, implementing enterprise-grade CI/CD with Blue/Green deployment becomes structured, secure, and scalable.

You now have:

Automated build
Automated deployment
Controlled traffic shift
Zero downtime strategy
Rollback mechanism

This architecture is production-ready for modern cloud-native applications

Step-by-Step Guide: OCI DevOps & Resource Manager Terraform Infrastructure Provisioning

 

Introduction

Infrastructure provisioning on Oracle Cloud Infrastructure (OCI) can be automated with Infrastructure as Code (IaC) using OCI DevOps, OCI Resource Manager, and Terraform — enabling CI/CD-driven deployments across environments.

In this blog, we’ll walk through a real-world, high level plan of provisioning OCI infrastructure using OCI DevOps build pipelines integrated with OCI Resource Manager (Plan & Apply).

High-Level Architecture

The overall workflow looks like this:

1. OCI DevOps Code Repository stores Terraform and pipeline artifacts

2. OCI DevOps Build Pipeline is triggered on code changes

3. Build Pipeline invokes OCI Resource Manager

4. Resource Manager runs Terraform Plan and Apply

5. Infrastructure is provisioned automatically

Step 1: Create OCI DevOps Code Repository

Start by creating a Code Repository inside your OCI DevOps Project. This repository will store:

• build_spec.yaml

• Terraform configuration files

Once created, clone the repository using Cloud Shell:

Authenticate using your OCI username and Auth Token.

Initially the repository will be blank and terraform codes will pushed to the repository using cloud shell.

Step 2: Create OCI DevOps Build Pipeline

Next, create a Build Pipeline in OCI DevOps. This pipeline will:

• Read Terraform artifacts

• Trigger OCI Resource Manager operations

You don’t need to configure all stages immediately; the pipeline will be connected later using triggers.

Step 3: Prepare Repository Structure

Organize your repository with a clean structure:

devops-repository/

├── build_spec.yaml

└── terraform/

└── resource_manager.tf

At present, the files are present locally in cloud shell but not on OCI Devops

Step 4: Upload Artifacts and Push to Repository

Add the Terraform and build specification files, then push them to the repository:

git add .

git commit -m "updated artifacts first time"--this will prompt for the username and password

git push -u origin main

Note:The build file has to be present in the root folder of the devops repository so that build pipeline can read it.

This ensures the build pipeline always pulls the latest Terraform configuration.

Step 5: Upload Terraform Artifacts to Object Storage

In this case, OCI Resource Manager requires Terraform configuration to be sourced from OCI Object Storage. You can also call resource manager directly from build pipeline.

1. Create an Object Storage bucket

2. Upload the Terraform artifacts (resource_manager.tf files)

Step 6: Create OCI Resource Manager Stack (CLI)

In this scenario, the stack cannot be created from the OCI Console. In such cases, use OCI CLI:

export compartment_id=<compartment_ocid>

export config_source_bucket_name=ORM_STACK

export config_source_namespace=<namespace>

export config_source_region=us-ashburn-1

export stack_display_name=ORM-STACK

export terraform_version=1.1.x

oci resource-manager stack create-from-object-storage \

--display-name $stack_display_name \

--compartment-id $compartment_id \

--config-source-bucket-name $config_source_bucket_name \

--config-source-namespace $config_source_namespace \

--config-source-region $config_source_region \

--terraform-version $terraform_version

Successful output returns the Stack OCID.

Step 7: Update build_spec.yaml

Update the build_spec.yaml file to reference the Resource Manager Stack OCID. This file defines:

• Build stages

• Resource Manager Plan

• Resource Manager Apply

This allows OCI DevOps to orchestrate Terraform execution automatically.

Step 8: Create Build Pipeline Trigger

Create a trigger that connects:

• Code Repository (main branch)

• Build Pipeline

Now, every git push automatically triggers infrastructure provisioning

Step 9: Commit and Trigger the Pipeline

Make final updates and push changes:

git add .

git commit -m "updated resource manager stack"

git push

Under the resource manager, we can see that both apply and plan jobs were triggered.

Note: In this case, the state file is internally being managed by Resource manager.

Thus every commit code pushed to devops will trigger the resource manager stack to create resources in OCI.

Benefits of This Approach

• Fully automated infrastructure provisioning

• Terraform state managed securely by OCI

• CI/CD driven infrastructure changes

• Repeatable, auditable deployments

• Reduced manual errors

---

Conclusion

By integrating OCI DevOps, OCI Resource Manager, and Terraform, you can achieve a powerful Infrastructure as Code (IaC) pipeline on Oracle Cloud. This setup is ideal for enterprises looking to standardize cloud provisioning with governance, automation, and scalability