-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
Description
Getting Started Script Checks (Release)
Part of #722
Caution
These steps are to be taken once the release branch exists.
In each operator repository, run the following commands. If any updates are
required, open a PR using the applicable link below.
git checkout release-25.7
# Some of the scripts are in a code/ subdirectory
# pushd docs/modules/superset/examples/getting_started
# pushd docs/modules/superset/examples/getting_started/code
pushd $(fd -td getting_started | grep examples); cd code 2>/dev/null || true
# Make a fresh cluster (~12 seconds)
kind delete cluster && kind create cluster
./getting_started.sh stackablectl
# Make a fresh cluster (~12 seconds)
kind delete cluster && kind create cluster
./getting_started.sh helm
popdTip
Create branches with predictable names so the links below work. Remember
to replace YY.M and YY.M.X with the appropriate release version:
git stash -m "unsaved work"
git fetch origin
git checkout -b fix/getting-started-25.7.0 origin/release-25.7Then use the links below to automatically create applicable PRs for each operator
using the PR template.
Getting Started Script Checks and Updates
Replace the items in the task list below with the applicable Pull Requests (if any).
- airflow-operator @NickLarsenNZ
-
commons-operator@NickLarsenNZ - druid-operator @NickLarsenNZ
- hbase-operator @maltesander
- hdfs-operator @maltesander
- hive-operator @NickLarsenNZ
- kafka-operator @maltesander
-
listener-operator - nifi-operator @maltesander
- opa-operator @Techassi
-
secret-operator - spark-k8s-operator @Techassi
- superset-operator @Techassi
- trino-operator @Techassi
- zookeeper-operator @Techassi
Reactions are currently unavailable