stackabletech / stackabletech/airflow-operator
Pod template names for the kubernetesExecutor should be specific to the airflow cluster
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 32
- Forks
- 6
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
Affected Stackable version
All that use kubernetesExecutor
Affected Apache Airflow version
All that use kubernetesExecutor
Current and expected behavior
It should be possible to run different clusters, both using the kubernetesExecutor, in the same namespace without clashes in the name of the pod template.
Possible solution
These constants should be combined with the cluster name to ensure uniqueness.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
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.
Research direction
Start with the constants in rust/crd/src/lib.rs linked by the issue and trace where they are used for Kubernetes pod templates. Verify how the cluster name is available at those call sites. Done means different Airflow clusters in the same namespace produce distinct pod template names without clashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100