Repository navigation
docs(proposals): could /k8s share native watches transparently - #73
Merged
Merged
Conversation
An investigation into serving many identical native WATCH requests from one upstream watch, by comparing resource versions. Nothing is implemented. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 27 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
docs/proposals/transparant-stream-cache.md: whether/k8scould serve many identical native WATCH requests from one upstream watch, using comparable resource versions. Nothing is implemented. The measurement of 200 native watchers it proposes is in progress and will follow.Release
Release PR #71 was built on
1bad87d, before the flaky-test fix in #72, so itskube adapter (go)check fails (TestGatewayRouteRefusesAndDisconnects). Release-please did not refresh #71 after #72: atest:commit is hidden from the changelog, so the release PR's content did not change and it was skipped.Close #71 before merging this PR, so that the next push to
main(merging this PR) makes release-please open a fresh release PR from currentmain, including #72. That PR's CI should then pass, and merging it releases 0.10.0.🤖 Generated with Claude Code