Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 11 Next »

Tool Chain

  • Login to Opsera → Toolchain → Enter an Application name & click “Create”

  • Select “Argocd” → Click “Confirm” → Click “Deploy Tool Selection”

  • Click “Registry” hyperlink populated → Platforms tab

Tool Registry

Argo Application registry

  • Select the Application from the drop-down → Verify the status

  • Once status is updated to “ACTIVE” → Click “Tools” tab

  • Search the Application name to find the tool

  • Click to launch the Tool Summary → Connections tab → “Secret Access Token” is prepopulated → “Test Connection”

Cluster Creation

  • Click “Clusters” tab → +New Argo Cluster

  • “Create New Argo Cluster” form → Select a Platform

    • AWS

    • Azure

AWS Cluster Creation

  • AWS → select the tool created (pre requisite)

  • [OPTIONAL] Enable IAM role and select value if required

  • Select the “Cluster” name

  • [OPTIONAL] Enable the radio button “Enable Argo Rollouts for Blue/Green Deployment” for using Blue/green deployment in pipeline step

  • This can be enabled by editing at later stage as well

  • Click “Create” → Cluster get created successfully

Azure Cluster Creation

  • Azure → select the tool created (pre requisite)

  • Select the “Cluster” name

  • [OPTIONAL] Enable the radio button “Enable Argo Rollouts for Blue/Green Deployment” for using Blue/green deployment in pipeline step

  • This can be enabled by editing at later stage as well

  • Click “Create” → Cluster get created successfully

Repositories Creation

  • Click “Repositories” tab-> +New Argo Repositories

  • Enter all the fields-> Click on “create”

  • Repository gets created successfully

Projects Creation

  • Click “Projects” tab-> +New Argo Projects

  • Enter the fields. Source field will have the created repository listed in the drop-down. Choose the created repository.

  • Give * as values in all the fields and NA in Blacklisted Namespaced Resources. Click “Create” button

  • Project gets created successfully

Application Creation

  • Click “Applications” tab-> +New Argo Application

  • Enter the fields. Project Name drop-down will list the project created in the projects tab. Choose the project from the drop-down

  • Cluster drop-down will have the list of AWS and Azure clusters created in the clusters tab. Select the cluster as per the requirement.

  • Give the GIT Path, GIT URL and Branch Name. Click “Create” button

  • Application gets created successfully

Pre-Requisite

AWS Tool Registration

  • Tool Registry → +New Tool

  • “Create New Tool” → Select “AWS Account”

  • Enter a tool name → Click “Create”

  • Summary of New tool created is displayed

  • Click “Connections” tab → Enter values → click save

  • Click “Test Connection”

Azure Tool Registration

  • Tool Registry-> New Tool

  • Create New Tool->Select Azure

  • Enter a tool name → Click “create”

  • Summary of new tool created is displayed.

  • Click “Connections” tab → Enter values → click save

  • Navigate to Applications tab-> Click “New Azure Application Credential”

  • Enter the details Name, Client ID, Client Secret and click on Create button

  • Application gets created

GitHub Tool Registration

  • Tool Registry-> New Tool

  • Create New Tool->Select GitHub

  • Enter a tool name → Click “Create”

  • Summary of New tool created is displayed

  • Click “Connections” tab → Enter values → click save

  • Click “Test Connection”

Jenkins Tool Registration

  • Tool Registry-> New Tool

  • Create New Tool->Select Jenkins

  • Enter a tool name → Click “Create”

  • Summary of New tool created is displayed

  • Click “Connections” tab → Enter values → click save

  • Click “Test Connection”

Pipeline

  • Flow: Build → Artifact → Deploy

    • Docker Build → ECR Push / ACR Push / Nexus Push → ArgoCD Deploy → Approval Gate(for Blue/green)

  • Docker Build Job Configuration sample screenshot

  • ECR Push step configuration sample screenshot

  • Nexus Push step configuration sample screenshot

RollBack

  • Argo deploy step configuration with Rollback sample screenshot

Rollback - When this step is enabled , rollback will happen automatically by deploying the artifact which is pointed to the artifacts.
Repository Tag - Select the repository or run to rollback to

Blue/Green Deployment

Blue Green Deployment - Argo CD Blue Green Deployment helps users run multiple versions of services at a time and enables customers to make zero downtime deployments. This toggle can be enabled to identify this deployment as a Blue Green Deployment.

Cluster Creation: Enable Blue green deployment radio button

  • Argo deploy step configuration with Blue Green Deployment sample screenshot

  • Add Approval gate after Argo deploy step - save & run the pipeline

  • Save the step → Click Start Pipeline

  • Pipeline Logs are updated as the pipeline runs

Argo Tool

  • Project is synced

  • Updated POD is pointing if approved for Blue/Green

  • Earlier POD will be pointing if rejected for Blue/Green

  • Specified roll back version will be deployed if Rollback enabled

  • No labels