[Improvement] Load the pods/services when initializing kyuubi service
- Dominant language
- Scala
- Stars
- 2.4k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.
### What would you like to be improved?
Seems that the informer will ignore the existing resources if no add/update/deletion.
It is better to load it one time when initializing the server.
### How should we improve?
Loading existing resource when initializing the server.
### Are you willing to submit PR?
- [X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
- [ ] No. I cannot submit a PR at this time.
Contributor guide
Research direction
Start by locating the informer and the server-initialization entry point responsible for pod and service resources. Check how existing resources are handled when no add, update, or deletion event occurs. Done means resources already present at startup are loaded and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, scala
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100