argocd to argocd

argocd/README.md

@@ -36,23 +36,17 @@ done
 find applications -name "*.yaml" -exec kubectl apply -n argocd -f {} \;
 ```
 
-### Repository secrets
-1. Generate keys locally with `ssh-keygen -f argo`
-2. Add `argo.pub` in `git.k-space.ee/<your>/<repo>` → Settings → Deploy keys
-3. Add `argo` (private key) at https://argocd.k-space.ee/settings/repos along with referenced repo.
 
-## Argo Deployment
-To deploy ArgoCD itself:
+## Cold start
+Normally ArgoCD deploys itself. Deploy ArgoCD out-of-bounds:
 
 ```bash
-helm repo add argo-cd https://argoproj.github.io/argo-helm
-kubectl create secret -n argocd generic argocd-secret # Empty secret for sessions
-kubectl label -n argocd secret oidc-client-argocd-owner-secrets app.kubernetes.io/part-of=argocd
-
-helm template -n argocd --release-name k6 argo-cd/argo-cd --include-crds -f values.yaml > argocd.yml
-kubectl apply -f argocd.yml -f application-extras.yml -f redis.yaml -f monitoring.yml -n argocd
-
-kubectl -n argocd rollout restart deployment/k6-argocd-redis deployment/k6-argocd-repo-server deployment/k6-argocd-server deployment/k6-argocd-notifications-controller statefulset/k6-argocd-application-controller
+kustomize build . --enable-helm | kubectl apply -f -
 ```
 
-WARN: ArgoCD doesn't host its own redis, Dragonfly must be able to independently cold-start.
+ArgoCD dependencies:
+- dragonfly (database)
+- passmower (auth)
+- traefik
+- #TODO: network...
+- gitea