⏲ Add initContainers to jobs to wait for dependencies instead of crashing (demos)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
Research direction
Start with demos/demos-v2.yaml and review the listed demos, using the linked nifi-kafka-druid-water-level-data serviceaccount.yaml and setup-superset.yaml as the reference. Check each applicable demo's Kubernetes manifests for dependency waits, namespace-scoped RBAC, and attached ServiceAccounts. Done means applicable demo pods wait for dependencies instead of showing premature CrashLoopBackOff failures.
Written by the indexing model from the issue text.
Description
[!NOTE]
This came out of the 25.3.0 Release Retro
Many demos have (Job or other) pods showing CrashLoopBackoff until their dependencies are satisfied.
This causes confusion when launching demos, especially during demo testing.
Each stack/demo should make use of initContainers to wait for dependencies to be satisfied without giving false failure indications.
[!TIP]
- Ensure a ServiceAccount is created and attached to applicable Pods, and give it permissions to watch Jobs/Pods so it can wait.
- Ensure the ServiceAccount doesn't specify a
namespaceso that the demo can be installed into any namespace.- Use namespace scoped RBAC (Role/RoleBinding instead of ClusterRole/ClusterRoleBinding).
List of demos
List generation command
cat demos/demos-v2.yaml | yq -yr '.demos | keys' | sed 's/^-/- [ ]/'
- airflow-scheduled-job
- 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
[!WARNING]
It is possible that some stacks also need the same treatment, but most of the waiting can be done in the actual demo.
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 13
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/demos
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/demos#402 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/demos#349 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/demos#293 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/demos#204 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/demos#202 · 3 comments ·
All issues in stackabletech/demos
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
bug ci-failure high priority
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vllm-project/vllm-omni#7972 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
amponce/archive-movie-browser#166 ·