resourceVersion from kubernetes doesn't exclude previous watch events
Open
Nobody has claimed this yet.
area-orchestrator
investigate
- Dominant language
- Go
- Stars
- 190
- Forks
- 24
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 18
Description
When watch API uses resourceVersion returned on CustomResourceList through List API, it still returns all the resources rather than excluding resources before resourceVersion.
cc: @karolz-ms
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 tracing the Kubernetes List and Watch API handling for CustomResourceList resourceVersion, then reproduce the behavior using a version returned by List. Done means a Watch started with that resourceVersion excludes events for resources that existed before it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100