Repository navigation
tracking: Test demos on nightly versions for 26.7.0 #426
Description
Activity
- changed the title
[-]chore(tracking): Test demos on nightly versions for 26.7.0[/-][+]tracking: Test demos on nightly versions for 26.7.0[/+]on Jul 9, 2026 🟢 trino-iceberg
Doc improvements here: #429
🟢 hbase-hdfs-load-cycling-data
🟢 airflow-scheduled-job
Fixes here: #431
Error with the run_dbt DAG
Exception rendering Jinja template for task 'dbt-test', field 'value'. Template: 'trino-coordinator-default-headless.{{ NAMESPACE }}.svc.cluster.local'Defined here:
demos/stacks/airflow/airflow.yaml
Line 206 in d01808c
Maybe we can use the
NAMESPACEorAIRFLOW__KUBERNETES_EXECUTOR__NAMESPACEenv vars instead?🟢 logging
🟢 jupyterhub-pyspark-hdfs-anomaly-detection-taxi-data
🟢 jupyterhub-keycloak
Initially errored due to this:
[I 2026-07-13 07:25:10.249 JupyterHub log:192] 200 GET /hub/spawn/justin.martin (justin.martin@::ffff:10.244.0.1) 27.63ms [I 2026-07-13 07:25:17.852 JupyterHub provider:661] Creating oauth client jupyterhub-user-justin.martin [W 2026-07-13 07:25:17.890 JupyterHub spawner:847] Received unhandled user_options for justin.martin: profile, cpu, image, memory [E 2026-07-13 07:25:17.891 JupyterHub user:1012] Unhandled error starting justin.martin's server: The 'cpu_guarantee' trait of a KubeSpawner instance expected a float, not the str '1'.Fixed by #434.
🟢 nifi-kafka-druid-earthquake-data
🟢 trino-taxi-data
🟢 nifi-kafka-druid-water-level-data
🟢 end-to-end-security
- Install succeeded, Trino access works as expected
- Superset responds with 500 error:
- The OIDC auth seems to not work due to
AttributeError: User object does not have roles or groups - This was caused by old cookies from previous testing. Deleting them fixed it.
- The OIDC auth seems to not work due to
🟢 argo-cd-git-ops
- Broken, working on a fix: fix(argo-cd):demo fixes for 26.7 #438
- works again
🟢 spark-k8s-anomaly-detection-taxi-data
Works
🟢 monitoring (stack)
🟢 observability (stack)
Works fine
Test procedure
# Installs to the default namespace stackablectl stack install observability# See values.yaml below stackablectl operator install --operator-values=values.yaml trinovalues.yaml:
# See: https://github.com/open-telemetry/opentelemetry-operator otelSidecarAnnotations: &otel-sidecar-annotations sidecar.opentelemetry.io/inject: default/otel-collector-grpc # See: https://docs.stackable.tech/home/stable/concepts/observability/telemetry/ telemetry: &operator-telemetry consoleLog: level: warn otelLogExporter: enabled: true level: info otelTraceExporter: enabled: true level: info instrumented-operator: &instrumented-operator podAnnotations: <<: *otel-sidecar-annotations telemetry: <<: *operator-telemetry # listener-operator: trino-operator: <<: *instrumented-operator
# See trino.yaml below kubectl apply -f trino.yamltrino.yaml
apiVersion: trino.stackable.tech/v1alpha1 kind: TrinoCluster metadata: name: simple-trino spec: image: productVersion: "481" clusterConfig: catalogLabelSelector: matchLabels: trino: simple-trino coordinators: roleConfig: listenerClass: external-unstable roleGroups: default: replicas: 1 workers: roleGroups: default: replicas: 1
🟢 tutorial-openldap
Ran this fine: https://docs.stackable.tech/home/nightly/tutorials/authentication_with_openldap/
Note: There are no dashboards in superset (we only deploy a stack, not a full demo).
🟢 data-lakehouse-iceberg-trino-spark
Done, closing.
- moved this from Development: In Progress to Development: Done in Stackable Engineering
on Jul 14, 2026
Part of stackabletech/issues#847
This is testing that the nightly release of the operators and products do not negatively impact
the products.
Note
Record the results (issues, anomalies, or success) during the process in a comment on this issue.
Eg:
The following emojis can be used to indicate the status:
hourglass: In progress / waitingred_circle: In progress with errorsorange_circle: Completed with minor issues or anomaliesgreen_circle: Completed without issues or errorsList of demos
Replace the items in the lists below with the applicable Pull Requests (if any). Also put your
GitHub handle next to the demo to indicate a particular demo was picked up for testing.
List of stacks
Similar to the demos above we need to test all stacks that don't have a demo.
Replace the items in the lists below with the applicable Pull Requests (if any). Also put your
GitHub handle next to the stack to indicate a particular stack was picked up for testing.
Tip
Some of the stacks have a tutorial to follow.
openldapNightly from Scratch Testing Instructions
These instructions are for deploying and completing the nightly demo from scratch.
Tip
Be sure to select the nightly docs version on https://docs.stackable.tech/home/nightly/demos/.