pre-release-upgrade-testing.md

name	Pre-Release Demo Upgrade Testing
about	This template can be used to track the upgrade testing of demos from stable to nightly leading up to the next Stackable release.
title	chore(tracking): Test demo upgrades on nightly versions for YY.M.X
labels	epic
assignees

Part of https://github.com/stackabletech/issues/issues/TRACKING_ISSUE

This is testing that upgrades from the stable release to 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:

:green_circle: **airflow-scheduled-job**

The CRD had been updated and I needed to change the following in the manifest:
...

The following emojis can be used to indicate the status:

• hourglass: In progress / waiting
• red_circle: In progress with errors
• orange_circle: Completed with minor issues or anomalies
• green_circle: Completed without issues or errors

List 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.

• airflow-scheduled-job
• argo-cd-git-ops
• data-lakehouse-iceberg-trino-spark
• end-to-end-security
• hbase-hdfs-load-cycling-data
• jupyterhub-keycloak
• jupyterhub-pyspark-hdfs-anomaly-detection-taxi-data
• logging
• nifi-kafka-druid-earthquake-data
• nifi-kafka-druid-water-level-data
• signal-processing
• spark-k8s-anomaly-detection-taxi-data
• trino-iceberg
• trino-taxi-data

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.

• monitoring
• observability
• openldap
• tutorial-openldap

Stable to Nightly Upgrade Testing Instructions

These instructions are for deploying and completing the stable demo, and then upgrading operators, CRDs, and products to the nightly versions well as upgrading the operators and CRDS.

Tip

Be sure to select the stable docs version on https://docs.stackable.tech/home/stable/demos/.

# For demo testing, , install demo (stable operators) for the stable release (OO.M).
stackablectl demo install <DEMO_NAME>

# For stack testing, install stack via
stackablectl stack install <STACK_NAME>

# --- IMPORTANT ---
# Run through the (still) nightly demo/stack instructions (refer to the list above).

# Install nightly version of operators
stackablectl release upgrade dev

# Bump every stacklet to the version that used by the nightly demo.
# Typically, this is the latest supported version.
kubectl patch hbaseclusters/hbase --type='json' -p='[{"op": "replace", "path": "/spec/image/productVersion", "value":"x.x.x"}]' # changed

# Check that the operator logs look good (no unexpected errors etc.)

# Run through the (still) nightly demo/stack instructions again.