stackabletech / stackabletech/operator-rs
Add method(s) for unversioned labels
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 167
- Forks
- 19
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
For listener-class integration, labels are owned by the listener-operator (if the operator is responsible for creating them).
e.g. the Airflow operator has:
// Used for PVC templates that cannot be modified once they are deployed
let unversioned_recommended_labels = Labels::recommended(build_recommended_labels(
airflow,
AIRFLOW_CONTROLLER_NAME,
// A version value is required, and we do want to use the "recommended" format for the other desired labels
"none",
&rolegroup_ref.role,
"none",
))
.context(LabelBuildSnafu)?;
This should be moved to operator-rs.
Contributor guide
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 by locating Labels::recommended and build_recommended_labels in operator-rs, then compare them with the Airflow operator example for listener-class integration. Move the unversioned-label construction into operator-rs and verify that operators can use it for labels that cannot be modified after deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100