GitOps with ArgoCD: Declarative Kubernetes Deployments

GitOps is a deployment methodology where every change to infrastructure and application state is committed to a Git repository. Kubernetes clusters are configured to automatically sync from this repository, providing auditability, easy rollbacks, and developer-friendly workflows.

ArgoCD Core Concepts

• Application: A mapping between a Git repo path and a Kubernetes cluster/namespace.
• Sync: The process of making cluster state match the desired state in Git.
• Self-heal: ArgoCD detects drift (manual kubectl changes) and automatically reverts.

Installing ArgoCD

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

Defining an Application

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: mirahlabs-api
  namespace: argocd
spec:
  source:
    repoURL: https://github.com/mirahlabs/infra
    path: k8s/api
    targetRevision: HEAD
  destination:
    server: https://kubernetes.default.svc
    namespace: production
  syncPolicy:
    automated:
      prune: true
      selfHeal: true

Progressive Delivery with Argo Rollouts

Combine ArgoCD with Argo Rollouts for canary releases. Deploy to 10% of traffic, validate metrics via Prometheus, then automatically promote to 100% if error rates stay below threshold—otherwise, auto-rollback.

Production Kubernetes Deployment and HPA Config

Here is an enterprise-grade Kubernetes YAML config defining a deployment spec with security context limits, CPU resources, and a HorizontalPodAutoscaler:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: mirahlabs-app
  namespace: production
spec:
  replicas: 3
  template:
    spec:
      securityContext:
        runAsNonRoot: true
        runAsUser: 10001
      containers:
      - name: web
        image: mirahlabs/web:latest
        resources:
          limits:
            cpu: "1"
            memory: 1Gi
          requests:
            cpu: 250m
            memory: 256Mi
---
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: mirahlabs-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: mirahlabs-app
  minReplicas: 3
  maxReplicas: 10
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 70

Cloud Infrastructure Performance Profile

Below is a comparative latency and throughput profile of this infrastructure pattern deployed under a simulated load of 10,000 concurrent requests:

US & UK DevOps Governance & Infrastructure Security

Automating infrastructure and deployment workflows must respect regional privacy laws. Under the UK GDPR and US California Consumer Privacy Act (CCPA), system administrators must ensure that data pipelines respect strict boundaries regarding where user telemetry and system logs are stored (data residency). Implementing secure deployment methods (such as the NIST Secure Software Development Framework - SSDF) ensures that pipeline secrets are securely managed in systems like HashiCorp Vault, and that container configurations undergo automated security scanning before being shipped to production environments.