Initial chart: odoosky-system namespace + local container registry (Distribution v2)

values.yaml

@@ -0,0 +1,36 @@
+# cluster-platform-v3 — defaults.
+#
+# Most knobs you'd flip live here so customer-cluster overlays can
+# tune sizing without forking the chart.
+
+namespace: odoosky-system
+
+registry:
+  enabled: true
+  image:
+    repository: registry
+    tag: "2.8"
+    pullPolicy: IfNotPresent
+  # ClusterIP service hostname:
+  #   registry.odoosky-system.svc.cluster.local:5000
+  # Used internally by build Jobs (push) and the Odoo Deployment's
+  # image volumes (pull). Plain HTTP — the registry never sees
+  # off-cluster traffic; node-side k3s registries.yaml whitelists
+  # the hostname for HTTP image pulls.
+  service:
+    port: 5000
+  # Storage. The registry survives node restarts but is recreatable —
+  # if the PVC is wiped, Tower's ensureAddonImage will rebuild any
+  # missing images from Gitea source on demand. So we don't need a
+  # large or replicated PV here.
+  persistence:
+    enabled: true
+    size: 10Gi
+    storageClass: ""  # "" = use the cluster's default; on k3s that's local-path
+  resources:
+    requests:
+      cpu: 50m
+      memory: 64Mi
+    limits:
+      cpu: 500m
+      memory: 256Mi