Run/check getting-started scripts

[NickLarsenNZ]

For each operator with a getting_started.sh script, run the following:

# 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

popd

Add the following checklist to the PRs:

```[tasklist]
### Run getting_started.sh via
- [ ] `stackablectl`
- [ ] `helm`
```

Tasks

Preview Give feedback

1. docs(getting-started): update stackablectl op install output airflow-operator#466
   2 of 2
   release/24.7.0 +1
   
2. docs(getting-started): update stackablectl op install output druid-operator#589
   2 of 2
   release/24.7.0 +1
   
3. docs(getting-started): update stackablectl op install output hbase-operator#528
   2 of 2
   release/24.7.0 +1
   
4. docs(getting-started): update stackablectl op install output hdfs-operator#553
   2 of 2
   release/24.7.0 +1
   
5. docs(getting-started): update stackablectl op install output hive-operator#489
   2 of 2
   release/24.7.0 +1
   
6. docs(getting-started): update stackablectl op install output kafka-operator#732
   2 of 2
   release/24.7.0 +1
   
7. docs(getting-started): update stackablectl op install output nifi-operator#646
   2 of 2
   release/24.7.0 +1
   
8. docs(getting-started): update stackablectl op install output opa-operator#601
   2 of 2
   release/24.7.0 +1
   
9. docs(getting-started): update stackablectl op install output spark-k8s-operator#432
   2 of 2
   release/24.7.0 +1
   
10. docs(getting-started): update stackablectl op install output superset-operator#515
    2 of 2
    release/24.7.0 +1
    
11. docs(getting-started): update stackablectl op install output trino-operator#616
    2 of 2
    release/24.7.0 +1
    
12. docs(getting-started): update stackablectl op install output zookeeper-operator#838
    2 of 2
    release/24.7.0 +1
    

Important

kafka-operator requires kafkacat (kcat in nix)

Note

The list above was generated by:

# cd to directory where you store the stackabletech repos locally
find -name 'getting_started.sh' -not -path './operator-templating/*' \
| cut -d/ -f2 \
| sort \
| sed 's/^/- [ ] /'

If you want to reuse a cluster, you can delete everything by doing:

# Delete Stackable Custom Resources
kubectl get crds | grep stackable | cut -d' ' -f1 | xargs -I {} kubectl -n default delete {} --all

# Delete well-known Kubernetes Resources in the default namespace
kubectl -n default delete all --all --grace-period 0

# Delete the operators
stackablectl release uninstall dev

# delete the Stackable Custom Resource Definitions
kubectl get crds | grep stackable | cut -d' ' -f1 | xargs -I {} kubectl delete crd {}

# You might need to check on any Helm releases
helm list
helm uninstall ...

[NickLarsenNZ]

Earlier in the process I was fixing as many lint issues as I could (even for files that weren't touched). But from now (kafka-operator), I will only fix what is required to speed up the process.