CD Workflow Without ArgoCD

In the realm of continuous delivery (CD), ArgoCD has emerged as a popular tool for managing Kubernetes deployments. However, there are situations where an alternative approach might be preferred. In this article, we will explore the concept of a CD workflow without ArgoCD and discuss how to achieve efficient and streamlined deployment processes.

Introduction

Continuous delivery is a crucial aspect of modern software development, ensuring that code changes can be rapidly and reliably pushed into production. While ArgoCD simplifies the management of Kubernetes deployments, there are scenarios where opting for a different CD workflow might be more suitable.

Traditional CD Approaches

Before delving into alternative workflows, it's essential to understand the traditional approaches to continuous delivery. Many organizations utilize tools like Jenkins, GitLab CI/CD, or GitHub Actions to automate the build, test, and deployment phases. These tools often integrate seamlessly with Kubernetes clusters, making them a natural choice for CD workflows.

Manual Deployment Steps

In a CD workflow without ArgoCD, manual deployment steps become more prominent. While this may sound counterintuitive in the age of automation, some scenarios, such as small-scale projects or specific security requirements, may necessitate a more hands-on approach.

Commands: Setting Up Kubernetes Resources

Let's start by setting up the Kubernetes resources manually. Use the following commands to create deployment files and apply them to your cluster:

# Create a deployment.yaml file
echo "apiVersion: apps/v1
kind: Deployment
metadata:
  name: example-deployment
spec:
  replicas: 3
  selector:
    matchLabels:
      app: example
  template:
    metadata:
      labels:
        app: example
    spec:
      containers:
      - name: example-container
        image: your-container-image:latest" > deployment.yaml

# Apply the deployment to the cluster
kubectl apply -f deployment.yaml

Step-by-Step Instructions: Verifying Deployment

Once the resources are applied, it's crucial to verify the deployment. Follow these steps to ensure that your application is running successfully:

1. Check the status of the deployment:

   kubectl get deployment example-deployment
   

2. Verify the pods' status:

   kubectl get pods -l app=example
   

3. Inspect the logs of a specific pod:

   kubectl logs <pod-name>
   

More Examples: Canary Deployments

In a CD workflow without ArgoCD, implementing canary deployments requires careful orchestration. Here's an example using Kubernetes native features:

1. Create a new deployment for the canary release:

   kubectl apply -f canary-deployment.yaml
   

2. Adjust the service to distribute traffic between the original and canary deployments.

   kubectl apply -f service-with-canary.yaml
   

3. Monitor the canary release and gradually increase traffic if successful.

Embracing Flexibility

While ArgoCD offers a robust solution for Kubernetes CD, a CD workflow without it allows for flexibility and adaptability to specific project requirements. Whether opting for manual steps or leveraging traditional CI/CD tools, the key is to choose a workflow that aligns with your project's goals and constraints.