stackabletech / stackabletech/operator-rs
Let product operators control product-specific vector config
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 167
- Forks
- 19
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
Currently, op-rs embeds a lot of product-specific knowledge. For example, there are several configuration bits that are only relevant to our specific deployment of OPA that are always embedded in the configuration (https://github.com/stackabletech/operator-rs/blob/3548b01e34c8e1b021b6ac6a2e3b91cc8d9ce2c8/crates/stackable-operator/src/product_logging/framework.rs#L755-L805).
It makes sense to offer a few defaults ("this is how we typically configure log4j to behave"), but the final say should be up to the operator and we definitely shouldn't have single-product configurations in the framework crate.
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 reading crates/stackable-operator/src/product_logging/framework.rs around lines 755-805, then trace how product-specific vector configuration is supplied to the framework. Done means operators can control these settings, reasonable defaults remain available, and product-specific configuration is no longer embedded in the framework crate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100