operator-framework / operator-framework/java-operator-sdk
Passing configuration as POJOs (v6)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 944
- Forks
- 242
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 43
Description
Currently, we have a configuration overrider approach, which would be nicer to have as a simple POJOs (+ Builder) to pass to the operator instance.
Note that at some point this configuration should override the onces coming from annotation to compute the final result. We have to also think about SB and mainly Quarkus integration.
see also:
https://github.com/operator-framework/java-operator-sdk/pull/3177
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
No files or tests are named. Start by tracing the existing configuration overrider and how configuration reaches the operator instance, then review annotation-derived configuration and the Spring Boot and Quarkus integration points. Done means a POJO-plus-Builder configuration path is defined, its precedence over annotation configuration is established, and the integrations are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes, spring-boot
- Domain
- backend, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100