forgejoadmin/gitops-apps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Argo CD Application manifests for cluster redeploy
6 commits 1 branch 0 tags 37 KiB
Find a file
forgejoadmin 68ccae15d3 masterone: prod-cluster deployment with Longhorn replicated storage (edge ingress on node03:443)
2026-08-16 15:41:57 +00:00
apps GitOps scaffold: Argo CD bootstrap, app-of-apps, example workload 2026-08-16 09:28:48 +00:00
bootstrap GitOps scaffold: Argo CD bootstrap, app-of-apps, example workload 2026-08-16 09:28:48 +00:00
clusters/default masterone: prod-cluster deployment with Longhorn replicated storage (edge ingress on node03:443) 2026-08-16 15:41:57 +00:00
README.md GitOps scaffold: Argo CD bootstrap, app-of-apps, example workload 2026-08-16 09:28:48 +00:00

README.md

GitOps scaffold for Rancher-managed Kubernetes

Flow: Developers/CI -> Forgejo -> Argo CD -> Rancher-managed clusters.

Kubernetes itself is NOT the backup. This repo (in Forgejo, backed up

by /root/forgejo/backup.sh) plus container images are the source of truth.

Layout:

bootstrap/ one-time Argo CD install + root App-of-Apps

apps/ one Argo CD Application per workload

clusters/ per-cluster config (registered Rancher clusters)

Usage on a NEW cluster:

1. kubectl apply -f bootstrap/argocd-namespace.yaml

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

3. kubectl apply -f bootstrap/repo-forgejo.yaml # registers THIS Forgejo repo

4. kubectl apply -f bootstrap/root-app.yaml # app-of-apps -> redeploys everything

5. (Rancher) cluster auto-registers; workloads converge from Git.