From 611e0c68ea52bcd74b94d0dbe75c9d7674dc6707 Mon Sep 17 00:00:00 2001 From: xeniape Date: Wed, 6 Aug 2025 09:43:27 +0200 Subject: [PATCH 1/2] chore: update docs to use bitnamilegacy --- .../pages/customization/add-stack.adoc | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/docs/modules/stackablectl/pages/customization/add-stack.adoc b/docs/modules/stackablectl/pages/customization/add-stack.adoc index 898662b8..ba41600e 100644 --- a/docs/modules/stackablectl/pages/customization/add-stack.adoc +++ b/docs/modules/stackablectl/pages/customization/add-stack.adoc @@ -28,7 +28,7 @@ stacks: - mycorp - warehouse manifests: - # We have Superset in out Stack, which needs a postgressql instance + # We have Superset in out Stack, which needs a postgresql instance # So let's install that first - helmChart: &template-postgresql-superset releaseName: postgresql-superset @@ -38,7 +38,18 @@ stacks: url: https://charts.bitnami.com/bitnami/ version: 11.0.0 options: - auth: + global: + security: + allowInsecureImages: true + image: + repository: bitnamilegacy/postgresql + volumePermissions: + image: + repository: bitnamilegacy/os-shell + metrics: + image: + repository: bitnamilegacy/postgres-exporter + auth: username: superset password: superset database: superset From a4ac116d575148078d945556df0638bd236a0759 Mon Sep 17 00:00:00 2001 From: xeniape Date: Wed, 6 Aug 2025 10:22:22 +0200 Subject: [PATCH 2/2] fix stack example --- .../pages/customization/add-stack.adoc | 64 +++++++++++-------- 1 file changed, 38 insertions(+), 26 deletions(-) diff --git a/docs/modules/stackablectl/pages/customization/add-stack.adoc b/docs/modules/stackablectl/pages/customization/add-stack.adoc index ba41600e..3e0583ba 100644 --- a/docs/modules/stackablectl/pages/customization/add-stack.adoc +++ b/docs/modules/stackablectl/pages/customization/add-stack.adoc @@ -21,42 +21,54 @@ As of writing a `stacks.yaml` file could look as follows: [source,yaml] ---- stacks: - mycorp-warehouse: + mycorp-warehouse: description: Internal stack we use to build our warehouses - stackableRelease: 22.09 # or use your custom release mycorp-release1 + stackableRelease: 25.7 # or use your custom release mycorp-release1 + stackableOperators: + - commons + - listener + - secret + - trino + - superset labels: - mycorp - warehouse manifests: - # We have Superset in out Stack, which needs a postgresql instance + # We have Superset in our Stack, which needs a postgresql instance # So let's install that first - - helmChart: &template-postgresql-superset - releaseName: postgresql-superset - name: postgresql - repo: - name: bitnami - url: https://charts.bitnami.com/bitnami/ - version: 11.0.0 - options: - global: - security: - allowInsecureImages: true - image: - repository: bitnamilegacy/postgresql - volumePermissions: - image: - repository: bitnamilegacy/os-shell - metrics: - image: - repository: bitnamilegacy/postgres-exporter - auth: - username: superset - password: superset - database: superset + - helmChart: https://my.corp/stacks/mycorp-warehouse/postgresql.yaml - plainYaml: https://my.corp/stacks/mycorp-warehouse/trino.yaml - plainYaml: https://my.corp/stacks/mycorp-warehouse/superset.yaml ---- +The referenced `helmChart` file above could look like the following: + +[source,yaml] +---- +releaseName: postgresql-superset +name: postgresql +repo: + name: bitnami + url: https://charts.bitnami.com/bitnami/ +version: 16.7.21 +options: + global: + security: + allowInsecureImages: true + image: + repository: bitnamilegacy/postgresql + volumePermissions: + image: + repository: bitnamilegacy/os-shell + metrics: + image: + repository: bitnamilegacy/postgres-exporter + auth: + username: superset + password: superset + database: superset +---- + == 2. Using the Custom `stacks.yaml` File After creating the `mycorp-stacks.yaml` file, it can be added to the available stacks in `stackablectl` via the CLI