diff --git a/stacks/end-to-end-security/superset.yaml b/stacks/end-to-end-security/superset.yaml index 9226aa10..4b213faa 100644 --- a/stacks/end-to-end-security/superset.yaml +++ b/stacks/end-to-end-security/superset.yaml @@ -5,7 +5,7 @@ metadata: name: superset spec: image: - productVersion: 3.1.3 + productVersion: 4.0.2 clusterConfig: listenerClass: external-unstable credentialsSecret: superset-credentials @@ -24,38 +24,38 @@ spec: # We need to restore the postgres state before the superset container itself starts some database migrations initContainers: # The postgres image does not contain curl or wget... - - name: download-dump - image: docker.stackable.tech/stackable/testing-tools:0.1.0-stackable0.1.0 - command: - - bash - - -c - - | - cd /tmp - curl --fail -O https://raw.githubusercontent.com/stackabletech/demos/main/stacks/end-to-end-security/postgres_superset_dump.sql.gz - gunzip postgres_superset_dump.sql.gz + - name: download-dump + image: docker.stackable.tech/stackable/testing-tools:0.2.0-stackable24.7.0 + command: + - bash + - -c + - | + cd /tmp + curl --fail -O https://raw.githubusercontent.com/stackabletech/demos/main/stacks/end-to-end-security/postgres_superset_dump.sql.gz + gunzip postgres_superset_dump.sql.gz - # We need to omit changing the users password, as otherwise the content in the Secrets does not match - # the actual password in Postgres. - grep -vwE '(CREATE ROLE postgres;|CREATE ROLE superset;|ALTER ROLE postgres|ALTER ROLE superset)' postgres_superset_dump.sql > /dump/postgres_superset_dump.sql - volumeMounts: - - name: dump - mountPath: /dump/ - - name: restore-postgres - image: docker.io/bitnami/postgresql:16.1.0-debian-11-r11 # Same image as the bitnami postgres helm-chart is using - command: - - bash - - -c - - | - psql --host postgresql-superset --user postgres < /dump/postgres_superset_dump.sql - env: - - name: PGPASSWORD - valueFrom: - secretKeyRef: - name: postgresql-superset - key: postgres-password - volumeMounts: - - name: dump - mountPath: /dump/ + # We need to omit changing the users password, as otherwise the content in the Secrets does not match + # the actual password in Postgres. + grep -vwE '(CREATE ROLE postgres;|CREATE ROLE superset;|ALTER ROLE postgres|ALTER ROLE superset)' postgres_superset_dump.sql > /dump/postgres_superset_dump.sql + volumeMounts: + - name: dump + mountPath: /dump/ + - name: restore-postgres + image: docker.io/bitnami/postgresql:16.1.0-debian-11-r11 # Same image as the bitnami postgres helm-chart is using + command: + - bash + - -c + - | + psql --host postgresql-superset --user postgres < /dump/postgres_superset_dump.sql + env: + - name: PGPASSWORD + valueFrom: + secretKeyRef: + name: postgresql-superset + key: postgres-password + volumeMounts: + - name: dump + mountPath: /dump/ volumes: - name: dump emptyDir: {} diff --git a/stacks/keycloak-opa-poc/superset.yaml b/stacks/keycloak-opa-poc/superset.yaml index a9ac38d0..fb94a18c 100644 --- a/stacks/keycloak-opa-poc/superset.yaml +++ b/stacks/keycloak-opa-poc/superset.yaml @@ -19,7 +19,7 @@ metadata: name: superset spec: image: - productVersion: 3.0.1 + productVersion: 4.0.2 clusterConfig: credentialsSecret: superset-credentials listenerClass: external-unstable