gsdavidp/home-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Argo CD configuration by enabling service in kube-vip daemonset, replacing argocd-ingress with argocd-server-lb, and updating documentation to reflect changes.

Browse Source
This commit is contained in:
Nikholas Pcenicni
2026-03-27 04:06:52 -04:00
parent cbbbf1cfc3
commit d39b253693
5 changed files with 24 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
talos/README.md
View File

@@ -112,15 +112,16 @@ nc -vz 192.168.50.230 6443
## 9) Argo CD via DNS host (no port)
Argo CD is exposed through Cilium Ingress with host:
Argo CD is exposed through a kube-vip managed LoadBalancer Service:
- `argo.noble.lab.pcenicni.dev`
Ingress manifest:
Manifests:
- `clusters/noble/bootstrap/argocd/argocd-ingress.yaml`
- `clusters/noble/bootstrap/argocd/argocd-server-lb.yaml`
- `clusters/noble/apps/kube-vip/vip-daemonset.yaml` (`svc_enable: "true"`)
After syncing manifests, create a Pi-hole DNS A record:
- `argo.noble.lab.pcenicni.dev` -> `192.168.50.230`
- `argo.noble.lab.pcenicni.dev` -> `192.168.50.231`