Addon initContainer materialization: per-addon image runs as initContainer + copies content into shared emptyDir mounted at /mnt/extra-addons

values.yaml

@@ -63,6 +63,31 @@ odoo:
   # Filestore PVC size (Odoo's /var/lib/odoo).
   filestoreSize: 10Gi
 
+# Addons selected for this instance. Each entry is a tagged image in
+# the cluster-local registry (deployed by cluster-platform-v3 chart).
+# The chart renders one initContainer per entry that copies the
+# addon's content into a shared volume; the Odoo container reads from
+# /mnt/extra-addons/<code>.
+#
+# Tower owns this list — it commits new entries to the tenant overlay
+# AFTER ensuring the corresponding image exists in the destination
+# cluster's registry (spawning a build Job from Gitea source if not).
+#
+# Schema:
+#   addons:
+#     - code: odoosky_demo
+#       version: "18.0.1.0.0"
+#       source: platform   # platform | tenant
+#       image: registry.odoosky-system.svc.cluster.local:5000/addons/odoosky_demo
+#
+# Empty list = no extra addons; only Odoo's built-in modules.
+addons: []
+
+# Path inside the Odoo container where addons are materialized.
+# Odoo's addons_path includes this dir; one folder per addon code.
+# Override only if you need a non-standard layout.
+addonsMountPath: /mnt/extra-addons
+
 postgres:
   image: postgres
   tag: "16-alpine"