Holds the Kubernetes manifests to set up the services on a local minikube cluster. This allows playing around and learning allows in a cheap and safe manner. Designed to be synced with ArgoCD running in the same cluster.

Use the CLI or UI to create a new ArgoCD Application for each directory with manifests in it.

Check the README in each dir to see if deploying those manifests will require secrets to be set or any other set up.

# Replace [SECRET] with a the sensitive value to store. Generates a base64-encoded secret to go into the secret manifest
 secret="$(echo -n '[SECRET]' | base64)"
echo "${secret}"

# Create opaque secret
cat > /tmp/k8s.secret.yaml << EOL
---
apiVersion: v1
kind: Secret
metadata:
  name: name-of-secret
data:
  SECRET: '${secret}'
EOL

kubectl apply -f /tmp/k8s.secret.yaml

# Will display newly created secret
kubectl get secrets/name-of-secret -o yaml

Go into the application directory, and run:

kustomize edit set image kustomize-managed-image-name='ghcr.io/[ACCOUNT]/[REPO]:[REVISION]'

Then commit and push the kustomization.yaml file.

It is allowed to dynamically change the deployed dev version of an ArgoCD application. Here is how:

argocd app set [APP]-dev --kustomize-image image-name-in-manifest=[HOST_AND_ACCOUNT]/[REPO]:[REVISION]
argocd app sync [APP]-dev

This is a convenient way of deploying a different version to a dev branch for testing.

Unset with:

argocd app unset donotdrivenow-dev --kustomize-image kustomize-managed-image-name

In all other cases, commit the change to the repo.