operator-framework / operator-framework/java-operator-sdk
Feature: tight up the integration with extra eventSources
Open
Nobody has claimed this yet.
feature
kind/feature
- Dominant language
- Java
- Stars
- 944
- Forks
- 242
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 43
Description
A controller can define additional eventSources as shown e.g. here
there are 2 improvements we can investigate:
- the watched resource should be easily accessible in the reconcile loop
- the generated Roles/RoleBindings etc. should take into account those resources too
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 with sample-operators/tomcat-operator/src/main/java/io/javaoperatorsdk/operator/sample/TomcatReconciler.java and inspect how its additional eventSources reach the reconcile loop. Trace the generated Roles and RoleBindings for those resources; done means the watched resource is accessible during reconciliation and the generated permissions include the additional eventSources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100