Initial Tower chart

values.yaml

@@ -0,0 +1,56 @@
+# admin-platform-v3 — Tower platform default values.
+
+backend:
+  enabled: true
+  image:
+    repository: docker.io/odoosky/tower
+    tag: "0.1.0"
+    pullPolicy: IfNotPresent  # IfNotPresent because the image is in
+                              # containerd's k8s.io namespace already
+                              # (lab1 single-server). Replace with
+                              # Always when we move to a real registry.
+  replicas: 1
+  resources:
+    requests:
+      cpu: 50m
+      memory: 64Mi
+    limits:
+      cpu: "1"
+      memory: 256Mi
+
+frontend:
+  # Off until Step 4 builds it. The chart slot is reserved here so
+  # turning it on later is a values-flip, not a chart edit.
+  enabled: false
+  image:
+    repository: docker.io/odoosky/tower-ui
+    tag: "0.1.0"
+  replicas: 1
+
+# Tower needs to talk to:
+#   - Gitea (create tenant repos, commit values.yaml)
+#   - ArgoCD (apply Application manifests)
+#
+# The credentials live in a K8s Secret in the same namespace, populated
+# from the ExistingSecret pattern (so they aren't checked into Git).
+# In Step 5+ we replace this with External Secrets sourcing from
+# OpenBao at vault.odoosky.org.
+config:
+  giteaURL: https://git.odoosky.org
+  giteaOrg: odoo-tower
+  chartRepo: instance-template-v3
+  argoCDURL: https://argocd.odoosky.org
+  argoCDUsername: admin
+  argoCDDestination: https://kubernetes.default.svc
+  argoCDProject: default
+  argoCDNamespace: argocd
+  tenantNamespace: tenants
+  # The Secret name (in the same namespace as Tower) that holds
+  # GITEA_TOKEN and ARGOCD_PASSWORD keys. Created out-of-band before
+  # this chart is applied.
+  existingSecret: tower-credentials
+
+ingress:
+  domain: tower.odoosky.org
+  certIssuer: letsencrypt-prod
+  entryPoint: websecure