Erich Blume
db37e7cc3e
1. Registering new ArgoCD apps from a feature branch: the app-of-apps "apps" Application is self-managing (re-reads apps.yaml on every sync, which pins targetRevision: main). So setting its revision to a branch doesn't stick across syncs, and new app definitions on a branch are invisible to the cluster via the normal flow. The goal card now documents the kubectl-apply + per-new-app `argocd app set --revision <branch>` workaround. 2. Tailscale device-name collision on cutover. The minikube immich ingress claims tailnet hostname "photos" (tls.hosts: [photos]). The ringtail ingress can't claim the same name while minikube's is alive (Tailscale enforces uniqueness). Staging uses tls.hosts: [photos-ringtail], with the rename to "photos" baked into immich-cutover-and-decommission step 2 + step 5. Card dependency graph unchanged; no new cards. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| authentik | ||
| configuration | ||
| dagger | ||
| deployment | ||
| forgejo-runner | ||
| grafana | ||
| immich | ||
| knowledgebase | ||
| mealie | ||
| operations | ||
| ringtail | ||
| runbooks | ||
| zot | ||