|
| 1 | +# Repository Rename: k3s-argocd-proxmox → talos-argocd-proxmox |
| 2 | + |
| 3 | +## Summary |
| 4 | + |
| 5 | +Successfully updated all repository references from the old name `k3s-argocd-proxmox` to the new name `talos-argocd-proxmox`. |
| 6 | + |
| 7 | +**Total Files Updated**: 12 files |
| 8 | + |
| 9 | +## Files Changed |
| 10 | + |
| 11 | +### ArgoCD Configuration (Critical - Affects GitOps) |
| 12 | +1. ✅ `infrastructure/controllers/argocd/root.yaml` |
| 13 | + - Root application that manages all other applications |
| 14 | + - **Action Required**: This will sync automatically, but verify after bootstrap |
| 15 | + |
| 16 | +2. ✅ `infrastructure/controllers/argocd/apps/projects.yaml` |
| 17 | + - Infrastructure, monitoring, and my-apps project definitions |
| 18 | + - Updated all 3 AppProject `sourceRepos` references |
| 19 | + |
| 20 | +3. ✅ `infrastructure/controllers/argocd/apps/infrastructure-appset.yaml` |
| 21 | + - ApplicationSet for infrastructure components |
| 22 | + - Updated both generator and source repoURL |
| 23 | + |
| 24 | +4. ✅ `infrastructure/controllers/argocd/apps/monitoring-appset.yaml` |
| 25 | + - ApplicationSet for monitoring stack |
| 26 | + - Updated both generator and source repoURL |
| 27 | + |
| 28 | +5. ✅ `infrastructure/controllers/argocd/apps/my-apps-appset.yaml` |
| 29 | + - ApplicationSet for user applications |
| 30 | + - Updated both generator and source repoURL |
| 31 | + |
| 32 | +### Documentation |
| 33 | +6. ✅ `README.md` |
| 34 | + - Updated documentation website link |
| 35 | + |
| 36 | +7. ✅ `.github/copilot-instructions.md` |
| 37 | + - Updated project header |
| 38 | + |
| 39 | +8. ✅ `docs/argocd.md` |
| 40 | + - Updated example ApplicationSet configuration |
| 41 | + |
| 42 | +9. ✅ `mkdocs.yml` |
| 43 | + - Updated repo_url and repo_name for documentation site |
| 44 | + |
| 45 | +### Scripts |
| 46 | +10. ✅ `scripts/update-pvcs-for-restore.sh` |
| 47 | + - Updated path reference (informational only) |
| 48 | + |
| 49 | +### Documentation Files (Local Paths - No Action Needed) |
| 50 | +These files reference local filesystem paths and don't need changes: |
| 51 | +- `docs/cilium-omni-setup.md` (local path) |
| 52 | +- `docs/INSTALL-CILIUM-NOW.md` (local path) |
| 53 | +- `docs/CILIUM-SUCCESS.md` (local path) |
| 54 | + |
| 55 | +## Next Steps |
| 56 | + |
| 57 | +### 1. Verify ArgoCD Will Sync ✅ |
| 58 | + |
| 59 | +After you bootstrap ArgoCD, it will automatically use the new repository URL: |
| 60 | + |
| 61 | +```bash |
| 62 | +# Bootstrap ArgoCD (if not done yet) |
| 63 | +cd /Users/mitchross/Documents/Programming/k3s-argocd-proxmox |
| 64 | + |
| 65 | +kustomize build infrastructure/controllers/argocd --enable-helm | kubectl apply -f - |
| 66 | +kubectl wait --for condition=established --timeout=60s crd/applications.argoproj.io |
| 67 | +kubectl wait --for=condition=Available deployment/argocd-server -n argocd --timeout=300s |
| 68 | +kubectl apply -f infrastructure/controllers/argocd/root.yaml |
| 69 | + |
| 70 | +# Watch applications sync from new repository |
| 71 | +kubectl get applications -n argocd -w |
| 72 | +``` |
| 73 | + |
| 74 | +### 2. Update Git Remote (If Cloned from Old URL) |
| 75 | + |
| 76 | +If your local repository is still pointing to the old URL: |
| 77 | + |
| 78 | +```bash |
| 79 | +# Check current remote |
| 80 | +git remote -v |
| 81 | + |
| 82 | +# Update to new repository name |
| 83 | +git remote set-url origin https://github.com/mitchross/talos-argocd-proxmox.git |
| 84 | + |
| 85 | +# Verify |
| 86 | +git remote -v |
| 87 | +``` |
| 88 | + |
| 89 | +### 3. Commit These Changes |
| 90 | + |
| 91 | +```bash |
| 92 | +git add -A |
| 93 | +git commit -m "chore: update repository references from k3s-argocd-proxmox to talos-argocd-proxmox" |
| 94 | +git push origin main |
| 95 | +``` |
| 96 | + |
| 97 | +### 4. Redeploy Documentation (Optional) |
| 98 | + |
| 99 | +If you're using GitHub Pages: |
| 100 | + |
| 101 | +```bash |
| 102 | +# The mkdocs.yml changes will be picked up automatically on next build |
| 103 | +# If you manually deploy: mkdocs gh-deploy |
| 104 | +``` |
| 105 | + |
| 106 | +## Verification Checklist |
| 107 | + |
| 108 | +- [x] ✅ All ArgoCD manifests updated |
| 109 | +- [x] ✅ All ApplicationSets point to new repo |
| 110 | +- [x] ✅ All AppProjects allow new repo URL |
| 111 | +- [x] ✅ Root application points to new repo |
| 112 | +- [x] ✅ Documentation links updated |
| 113 | +- [x] ✅ MkDocs configuration updated |
| 114 | +- [ ] ⏳ Git remote updated (do this manually if needed) |
| 115 | +- [ ] ⏳ Changes committed and pushed |
| 116 | +- [ ] ⏳ ArgoCD applications synced successfully |
| 117 | + |
| 118 | +## Important Notes |
| 119 | + |
| 120 | +### ArgoCD Behavior |
| 121 | + |
| 122 | +- **Automatic Sync**: If you have `automated: true` in your ApplicationSets (you do), ArgoCD will automatically pull from the new repository URL after you apply the updated manifests |
| 123 | +- **No Manual Intervention**: The applications will continue to work seamlessly |
| 124 | +- **History Preserved**: Git history and commit SHAs remain the same, so ArgoCD won't see this as a breaking change |
| 125 | + |
| 126 | +### GitHub Pages |
| 127 | + |
| 128 | +If you have GitHub Pages configured for documentation: |
| 129 | +- The URL will change from `https://mitchross.github.io/k3s-argocd-proxmox` to `https://mitchross.github.io/talos-argocd-proxmox` |
| 130 | +- You may want to set up a redirect on the old site or update any bookmarks |
| 131 | + |
| 132 | +## What Wasn't Changed (Intentionally) |
| 133 | + |
| 134 | +### Local Filesystem Paths |
| 135 | +These documentation files contain local paths that don't need updating: |
| 136 | +- `docs/cilium-omni-setup.md`: `/Users/mitchross/Documents/Programming/k3s-argocd-proxmox` |
| 137 | +- `docs/INSTALL-CILIUM-NOW.md`: `/Users/mitchross/Documents/Programming/k3s-argocd-proxmox` |
| 138 | +- `docs/CILIUM-SUCCESS.md`: `/Users/mitchross/Documents/Programming/k3s-argocd-proxmox` |
| 139 | + |
| 140 | +These are fine as-is since they're just examples showing the working directory. |
| 141 | + |
| 142 | +## Testing |
| 143 | + |
| 144 | +After committing and pushing, verify everything works: |
| 145 | + |
| 146 | +```bash |
| 147 | +# 1. Check ArgoCD applications are healthy |
| 148 | +kubectl get applications -n argocd |
| 149 | + |
| 150 | +# 2. Check ApplicationSets are generating applications |
| 151 | +kubectl get applicationsets -n argocd |
| 152 | + |
| 153 | +# 3. Verify sync status |
| 154 | +kubectl get applications -n argocd -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.sync.status}{"\n"}{end}' |
| 155 | + |
| 156 | +# All should show "Synced" |
| 157 | +``` |
| 158 | + |
| 159 | +## Rollback Plan (If Needed) |
| 160 | + |
| 161 | +If something goes wrong, you can quickly rollback: |
| 162 | + |
| 163 | +```bash |
| 164 | +# Revert the commit |
| 165 | +git revert HEAD |
| 166 | + |
| 167 | +# Or manually change URLs back in ArgoCD manifests |
| 168 | +# Then apply: kubectl apply -f infrastructure/controllers/argocd/ |
| 169 | +``` |
| 170 | + |
| 171 | +--- |
| 172 | + |
| 173 | +**Status**: ✅ All repository references updated successfully! |
| 174 | +**New Repository**: https://github.com/mitchross/talos-argocd-proxmox |
0 commit comments