gitops-playground-apps

Application stack for used with K3d setup gitops-playground

---

Use case

Experimenting and learning new projects/technology locally, but retaining a way to easily destroy and recreate in the future. Only the base applications are configured to auto-sync, so as to give the user the option to select which applications they want to run by synchronizing in the ArgoCD interface. The idea could be that a developer wants to work locally on a subset of microservices and doesn't have a requirement to run an entire application stack.

---

Requirements

• Step (Optional. Only if using Linkerd)

---

Environments

The template works on a branching strategy whereby each environment can be developed and merged upstream, with main/master being the production environment. env2 is used as a placeholder for this, but primarily for the playground aspect local is used.

---

The application stack

Applications are deployed using an ArgoCD application spec that is templated as a helm deployment following the app of apps pattern

Base

• Ingress-Nginx
• Prometheus-stack

Optional

• Argo-events
• Argo-rollouts
• Argo-workflows
• Argo-image-updater

---

Argo Events Build webhook

Simple webhook to mock a git triggered build (in the event that there is no public facing endpoint for github to interact with)

curl -X POST -H "Content-Type: application/json" -d '{"message":"build something"}' http://localhost:8080/demo-build-webhook

Generate some simple traffic for simulating canary deployment (Using argo-rollouts)

k6 run k6-tests/hugo-smoke.js

---

Managing secrets

I was originally using Seal-secrets for this project in keeping with the GitOps mandate. But due to the disposable nature of the cluster (which then creates a new encryption key) it's become a bit tedious having to commit the change back into git each time the cluster is recreated.
For now the secret is create with a script outside of git. I'll look to revisit this in the future.

Sample ArgoCD boot strap config

project.yaml

apiVersion: argoproj.io/v1alpha1
kind: AppProject
metadata:
  name: playground-project
  namespace: argocd
spec:
  description: playground project
  sourceRepos:
  - 'https://github.com/helm/charts.git'
  - 'https://github.com/argoproj/argocd-example-apps.git'
  - 'https://github.com/davidwmcneill/gitops-playground-apps.git'
  destinations:
  - namespace: '*'
    server: https://kubernetes.default.svc

  clusterResourceWhitelist:
  - group: '*'
    kind: '*'

app-of-apps.yaml

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: app-of-apps-local
  namespace: argocd
spec:
  destination:
    namespace: argocd
    server: 'https://kubernetes.default.svc'
  project: playground-project
  source:
    path: argocd
    repoURL: 'https://github.com/davidwmcneill/gitops-playground-apps.git'
    targetRevision: local
    helm:
      valueFiles:
      - local.yaml
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true
      - ApplyOutOfSyncOnly=false

---

Reference

• K3d - K3s docker wrapper
• Sealed-secrets - Manage secrets in git
• Helm - Kubernetes package manager
• Argocd - Gitops operator
• Argo-Rollouts - Advanced deployment
• Argo-Workflows - Workflow engine
• Argo-Events - Event driven workflow automation
• K6 - Loadtesting tool
• Tilt - Dev build tool for k8s
• Linkerd - Service mesh