added vault and contour

values/incubator-infra-k8s-admin-prd-ase1-values.yaml

@@ -49,4 +49,26 @@ appSpec:
     # looks like clearing them, which the API correctly refuses). The
     # Deployment-only fix now lives as a per-resource sync-option
     # annotation in helm-overrides/k8s-admin-prd-ase1/gitea/custom-values.yaml
-    # (deployment.annotations), which only Replaces the Deployment.
+    # (deployment.annotations), which only Replaces the Deployment.
+  - name: vault
+    # Adopting the running production-mode Vault (helm release "vault" in
+    # namespace "vault", chart 0.34.1 — see helm-templates/vault/Chart.yaml).
+    # It's already initialized and unsealed; this Application only manages
+    # Vault's Deployment/config, never its data or seal state. Review the
+    # first diff carefully before syncing — this is the highest-consequence
+    # adoption in this repo so far.
+    nameOverride: vault
+    namespace: vault
+    chartDir: vault
+    valuesDir: vault
+  - name: contour
+    # Adopting the running ingress (helm release "contour" in namespace
+    # "projectcontour", chart 0.7.0 — the OFFICIAL projectcontour chart,
+    # not the Bitnami one that used to be wired up as helm-templates/contour
+    # — see the note in that Chart.yaml and claude.md issue #4). This is
+    # the ingress path for every other Application in this repo — review
+    # the diff before syncing, same caution as vault.
+    nameOverride: contour
+    namespace: projectcontour
+    chartDir: contour
+    valuesDir: contour