Continuous Deployment via Argo (GitOps)

Continuous Deployment via Argo

Git Configuration

1. Login to Argo tool and navigate to Settings (gear icon)

Open

2. Navigate to Repositories

Open

3. Click ‘+ CONNECT REPO USING HTTPS’ button (or ‘+ CONNECT REPO USING SSH’ as per requirement)

4. Enter the details:

5. The added repository details are reflected in Repositories

Project Configuration

1. Navigate to Repositories → Projects

2. Click ‘New Project’ button.

3. Enter the required details and save

4. The saved project is reflected

Kubernetes Cluster Configuration

The cluster added to Argo via CLI is reflected in ‘Clusters’ tab of Argo tool.

AWS EKS

1. Download the AWS CLI Installing or updating to the latest version of the AWS CLI - AWS Command Line Interface

2. Configure AWS credential to AWS CLI.
   
   

   $ aws configure AWS Access Key ID [****************QW7K]: AWS Secret Access Key [****************zsTw]: Default region name [us-east-2]: Default output format [None]:

3. Make sure Kubernetes Cluster is already present or create a new one.

4. Install ArgoCD CLI (vesion: v2.0.4) on your system from https://argoproj.github.io/argo-cd/cli_installation/

5. Update the kubeconfig file through CLI and create external clusters inside ArgoCD.
   
   

   # Update the kubeconfig file for auth. aws eks update-kubeconfig --region us-east-2 --name cluster-name # Login to argocd server through cli argocd login <argocd_server_url> --password <password> --username <username> # add external cluster through cli to argocd argocd cluster add <kube_context> --name <cluster-name> Note: kube_context format for EKS: arn:aws:eks:<region>:<account_id>:cluster/<cluster_name>

6. Verify the external clusters inside ArgoCD UI.
   
   

Azure AKS

1. Download the Azure CLI How to install the Azure CLI

2. Authenticate the Azure CLI to the azure account.
   
   

   $ az login A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with `az login --use-device-code`.

3. Make sure Kubernetes Cluster already present or create a new one.

4. Install ArgoCD CLI (vesion: v2.0.4) on your system from https://argoproj.github.io/argo-cd/cli_installation/

5. Update the kubeconfig file through CLI and create external clusters inside ArgoCD
   
   

6. Verify the external clusters inside ArgoCD UI.
   
   

    

Nexus Prerequisites

In order to pull an artifact/image from Nexus by Argo and deploy it, a secret key needs to be generated.

1. Generate a secret token from Kubernetes for Nexus.
   
   

2. Copy the generated secret token.

3. Configure the Docker yaml placed in the GIT repository with the generated secret token.
   It will look similar to lined 6-17 below:

Opsera Configurations

Tool Registry Configuration

1. Login to https://portal.opsera.io -> Tool Registry -> Click ‘+New Tool’ Button

2. Locate ‘Argo’ tool and click ‘Select Tool’ button to open Create New Tool form.

Provide Tool Name and any other tool details.

3. Click ‘Create’ button for the tool to be registered

4. In ‘Connections’ tab, enter connection details:
Argo Container URL, Argo User ID and Argo Password and click the ‘Save’ button.

5. Click 'Test Connection’ button to ensure the credentials are valid and the connection succeeds.

6. Navigate to ‘Clusters’ tab and click ‘+ New Argo Clusters' button.

7. Provide selections for drop-downs and click ‘Create’ button. Once a cluster has been created it will become available for selections in ‘Applications’ tab. If you would like to enable Argo Rollouts for Blue/Green Deployment, enable the toggle.

6. Navigate to ‘Application’ tab and Click ‘+New Argo Application’ button.

7. Select correct values from the provided fields. The cluster added in ‘Clusters’ tab will be available in the ‘Cluster’ drop-down.

8. Navigate to git ‘Repositories’ tab, click ' + New Argo Repositories' button and provide values for the following fields:

• Name - Provide a unique name for the new Argo repository.

• SCM type - Select the source control management tool to configure. Choose from Bitbucket, Github or Gitlab.

• SCM Tool - Select your configured source control management tool provided in the drop down.

• Repository Name - Select a repository, fetched from the selected source control management tool.

9. Navigate to ‘Projects’ tab, click ‘+ New Argo Project’ button and provide values for the following fields:

• Name - Create a unique name for the Argo project.

• Description

• Sources - The drop down list will provide sources from the repository selected in the git Repositories tab.

• Destinations - *

• Whitelisted Cluster Resources - *

• Blacklisted Namespaced Resources - *

• Whitelisted Namespaced Resources - *

Click ‘Save’ button to save the project.

Pipeline Setup and Configuration

Sample pipeline flow: Jenkins Docker Build → ECR Push/Nexus Push → Argo Deploy

1. Jenkins step - Docker Build Job

Sample Configuration screenshot of Docker build step:

2. ECR Push step configuration sample screenshot:

3. Nexus Push step configuration sample screenshot:

4. 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.

5. Argo deploy step configuration with Blue Green Deployment sample screenshot:

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

Pipeline: Enable Blue green deployment radio button

6. Save the step

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

Approve or Reject after deployment for Argo to point to latest pod or old pod

Pipeline Logs

Pipeline Logs are updated as the pipeline runs.

Pipeline logs successful run screenshot:

Argo Validation

1. Login to Argo Tool and verify the application reflected and synced