ahmza.com/k8s-starter-pack
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Point Argo CD at Gitea and configure storage workers

Browse Source
This commit is contained in:
ahmza
2026-09-03 01:54:37 +01:00
parent a5ddf11992
commit b6f8f36c5b
8 changed files with 47 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files
argocd/README.md
+8 -6
View File
@@ -83,16 +83,18 @@ argocd account update-password
[`app-of-apps/app-of-apps.yaml`](app-of-apps/app-of-apps.yaml) is the one
manifest in this whole repo you apply by hand — everything after it, Argo
CD applies for you. First, every Application manifest needs its own
`repoURL` pointed at your fork (they don't inherit it from each other):
CD applies for you. Every Application manifest has its own `repoURL`
because child Applications do not inherit it from their parent. Verify they
all point at this cluster's public Gitea repository:
```sh
grep -rl YOUR_GITHUB_USERNAME .
grep -R "repoURL:" argocd/app-of-apps apps/*.yaml
git ls-remote https://tea.ahmza.com/ahmza/k8s-starter-pack.git HEAD
```
Edit `spec.source.repoURL` in each file that command finds, commit, and
push — the child Applications are read from Git, not your local disk, so
this has to land in your fork before the next step. Then:
The remote check must succeed without credentials. Commit and push any
pending changes before continuing — child Applications read from Git, not
your local disk. Then:
```sh
kubectl apply -f argocd/app-of-apps/app-of-apps.yaml