Erich Blume
7573a72318
GitOps decommission of immich + immich-pg on minikube:
- Delete argocd/apps/immich.yaml
- Delete argocd/manifests/immich/ entirely
- Delete argocd/manifests/databases/{immich-pg,external-secret-immich-borgmatic,service-immich-pg-tailscale}.yaml
- Remove those entries from databases/kustomization.yaml
Add ringtail-side immich-pg Tailscale LoadBalancer Service (hostname
"immich-pg") so borgmatic can keep using the same FQDN for nightly
backups. This claims the device name freed by deleting the minikube
service.
The ringtail manifest path stays as argocd/manifests/immich-ringtail/
and the ArgoCD app stays as immich-ringtail — renaming would force a
cascading delete + recreate, with a window where live resources
disappear.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
24 lines
694 B
YAML
24 lines
694 B
YAML
# Tailscale LoadBalancer for immich-pg PostgreSQL access on ringtail.
|
|
# Canonical hostname: immich-pg.tail8d86e.ts.net (claimed from the
|
|
# minikube side after the minikube service was removed during the
|
|
# immich-to-ringtail migration). Borgmatic on indri uses this
|
|
# hostname for nightly backups.
|
|
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
name: immich-pg-tailscale
|
|
namespace: databases
|
|
annotations:
|
|
tailscale.com/hostname: "immich-pg"
|
|
tailscale.com/proxy-class: "default"
|
|
spec:
|
|
type: LoadBalancer
|
|
loadBalancerClass: tailscale
|
|
selector:
|
|
cnpg.io/cluster: immich-pg
|
|
role: primary
|
|
ports:
|
|
- name: postgresql
|
|
port: 5432
|
|
targetPort: 5432
|
|
protocol: TCP
|