Point comments at paths that still exist after the homelab overrides were removed

References to helm-overrides/k8s-admin-prd-ase1 now either name the
homelab repo that still has that folder, or point at the GKE equivalent
under gke-toolshed-prd-usc1. Comments only; no rendered values change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fn2kUxyYNY4ApytbLiGWeY

helm-overrides/gke-toolshed-prd-usc1/argocd-admin-prd/custom-values.yaml

@@ -1,5 +1,6 @@
 argo-cd:
-  # GKE counterpart of helm-overrides/k8s-admin-prd-ase1/argocd-admin-prd.
+  # GKE counterpart of the homelab's argocd-admin-prd override
+  # (k8s-admin-prd-ase1, in the homelab devops-infra-helm-charts repo).
   #
   # Installed once by hand with `helm install argocd-admin-prd` (namespace
   # "argocd"), then manages itself through the argocd Application in

helm-overrides/gke-toolshed-prd-usc1/cert-manager/custom-values.yaml

@@ -1,6 +1,6 @@
 # GKE values for the vendored cert-manager chart (helm-templates/cert-manager,
-# v1.20.1). Written fresh rather than copied from k8s-admin-prd-ase1, whose
-# file was never adapted from the fleet: it pulls images from a private
+# v1.20.1). Written fresh rather than copied from the homelab's
+# k8s-admin-prd-ase1 override, whose file was never adapted from the fleet: it pulls images from a private
 # Meesho Artifact Registry and pins pods to a "dedicated: devops" node pool
 # that does not exist here.
 #

helm-overrides/gke-toolshed-prd-usc1/contour/custom-values.yaml

@@ -1,6 +1,6 @@
 contour:
-  # GKE counterpart of helm-overrides/k8s-admin-prd-ase1/contour. Same
-  # official projectcontour chart (0.7.0, see helm-templates/contour), but
+  # GKE counterpart of the homelab's contour override (k8s-admin-prd-ase1,
+  # in the homelab devops-infra-helm-charts repo). Same official projectcontour chart (0.7.0, see helm-templates/contour), but
   # exposed the opposite way.
   #
   # The homelab binds Envoy to node ports 80/443 with hostPort, because

helm-overrides/gke-toolshed-prd-usc1/gitea/custom-values.yaml

@@ -1,6 +1,7 @@
 gitea:
-  # GKE counterpart of helm-overrides/k8s-admin-prd-ase1/gitea — same
-  # SQLite/no-cache shape, with what differs on GKE called out inline.
+  # GKE counterpart of the homelab's gitea override (k8s-admin-prd-ase1,
+  # in the homelab devops-infra-helm-charts repo) — same SQLite/no-cache
+  # shape, with what differs on GKE called out inline.
   #
   # Installed once by hand with `helm install gitea` (release "gitea",
   # namespace "gitea"), then adopted by ArgoCD via the nameOverride in

helm-overrides/gke-toolshed-prd-usc1/harbor/custom-values.yaml

@@ -1,6 +1,6 @@
 harbor:
-  # GKE counterpart of helm-overrides/k8s-admin-prd-ase1/harbor, same chart
-  # (1.19.1), with one fundamental difference: this Harbor is served over
+  # GKE counterpart of the homelab's harbor override (k8s-admin-prd-ase1,
+  # in the homelab devops-infra-helm-charts repo), same chart (1.19.1), with one fundamental difference: this Harbor is served over
   # real TLS, and it has to be.
   #
   # The homelab runs Harbor on plain HTTP and works around containerd's

helm-overrides/gke-toolshed-prd-usc1/jenkins/custom-values.yaml

@@ -1,6 +1,6 @@
 jenkins:
-  # GKE counterpart of helm-overrides/k8s-admin-prd-ase1/jenkins, same chart
-  # (5.8.58). Dynamic Kubernetes build agents, so idle cost is the
+  # GKE counterpart of the homelab's jenkins override (k8s-admin-prd-ase1,
+  # in the homelab devops-infra-helm-charts repo), same chart (5.8.58). Dynamic Kubernetes build agents, so idle cost is the
   # controller alone.
   #
   # Every plugin pin below is carried over deliberately, not copied

helm-overrides/gke-toolshed-prd-usc1/vault/custom-values.yaml

@@ -1,6 +1,6 @@
 vault:
-  # GKE counterpart of helm-overrides/k8s-admin-prd-ase1/vault, same chart
-  # (0.34.1) and same shape — production mode, file storage, standalone, no
+  # GKE counterpart of the homelab's vault override (k8s-admin-prd-ase1,
+  # in the homelab devops-infra-helm-charts repo), same chart (0.34.1) and same shape — production mode, file storage, standalone, no
   # HA — with one substantial difference: this Vault unseals itself from
   # Cloud KMS instead of by hand.
   #

helm-templates/argo-cd/README.md

@@ -7,6 +7,12 @@ ArgoCD is the one thing in this repo that can't bootstrap itself via
 GitOps — it has to exist before it can manage anything, including itself —
 so every step here is a manual, imperative command run once.
 
+> **Homelab only.** Every `k8s-admin-prd-ase1` path below lives in the
+> homelab `devops-infra-helm-charts` / `devops-infra-argo-config` repos, not
+> in this GCP copy. On GKE, ArgoCD is installed by Terraform
+> (`toolshed-gke-infra/envs/prod/20-bootstrap/argocd.tf`), and its values
+> live in `helm-overrides/gke-toolshed-prd-usc1/argocd-admin-prd/`.
+
 ## 0. Full uninstall (only if resetting)
 
 ```bash

helm-templates/postgresql/values.yaml

@@ -1,5 +1,5 @@
 # Chart defaults. Real configuration lives in
-# helm-overrides/k8s-admin-prd-ase1/postgresql/custom-values.yaml.
+# helm-overrides/gke-toolshed-prd-usc1/postgresql/custom-values.yaml.
 
 fullnameOverride: postgresql
 

helm-templates/redis/values.yaml

@@ -1,5 +1,5 @@
 # Chart defaults. Real configuration lives in
-# helm-overrides/k8s-admin-prd-ase1/redis/custom-values.yaml.
+# helm-overrides/gke-toolshed-prd-usc1/redis/custom-values.yaml.
 
 fullnameOverride: redis