Extend ArgoCD GitOps demo with DataOps
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- kubernetes, terraform
- Domain
- data-engineering, devops, infrastructure
Research direction
Start by reading the existing ArgoCD demo and the “trino-taxi-data” demo, then identify how the demo handles its cluster and sealed secrets. Define the DataOps scope around integrating the demo, adding the Airflow DAG for Trino jobs, deploying artifacts from source to target, and documenting the completed workflow.
Written by the indexing model from the issue text.
Description
Stackable data platforms are defined declaratively, enabling automated, standardized, and efficient deployments.
This demo showcases an exemplary GitOps setup for the Stackable data platform using e.g. ArgoCD and distinct Dev/Prod stages. This approach offers consistency, version control, speed, enhanced collaboration, robust security, and observability, making it easier for teams to manage infrastructure as code and adopt Stackable.
For new, non-advanced users, this setup simplifies the learning curve, reduces manual errors, and provides a clear pathway to modern DevOps/GitOps practices.
Prerequisites
- no Dev/Prod stages (only 1 cluster)
- without terraform
- including secrets via git (sealed secrets)
Tasks - DataOps
- Integrate existing demo "trino-taxi-data" in ArgoCD demo
- Add a new airflow DAG to submit Trino jobs (create schema, create table,...)
- PLACEHOLDER: Show progress and refine next step
- Deploy new artifacts via dataops from source to target
- Documentation
- 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 ·
-
release-retro/25.3.0
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/demos#208 ·
-
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
removeToken
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cowprotocol/token-lists#1514 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
anomalyco/models.dev#7670 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cisagov/cyhy-reports#149 · 3 comments ·
-
remove entry
Difficulty 1/5 Under an hour Newbie friendliness 74/100