Prevent cross-service revision traffic routing#16294
Merged
knative-prow[bot] merged 1 commit intoknative:mainfrom Dec 17, 2025
Merged
Prevent cross-service revision traffic routing#16294knative-prow[bot] merged 1 commit intoknative:mainfrom
knative-prow[bot] merged 1 commit intoknative:mainfrom
Conversation
Services can no longer route traffic to revisions belonging to different services. When a Service-owned Route references a revision with a different serving.knative.dev/service label, the Route will show Ready=False with reason RevisionNotOwned. Standalone Routes (not owned by a Service) are unaffected and can still reference any revision.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #16294 +/- ##
==========================================
+ Coverage 80.10% 80.12% +0.02%
==========================================
Files 215 215
Lines 13332 13360 +28
==========================================
+ Hits 10679 10705 +26
- Misses 2294 2296 +2
Partials 359 359 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
Author
|
/retest |
1 similar comment
Contributor
Author
|
/retest |
Member
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, linkvt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
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.
Fixes #11916
Services can no longer route traffic to revisions belonging to different services. When a Service-owned Route references a revision with a different serving.knative.dev/service label, the Route will show Ready=False with reason RevisionNotOwned.
Standalone Routes (not owned by a Service) are unaffected and can still reference any revision.
Changes
RevisionNotOwnedcondition reason when validation failsOpen Question
Should we also add validation at the webhook level for faster user feedback?
This would require using the revision informer in the webhook which would probably increase the memory footprint a bit (didn't test it).
The current implementation validates at reconciliation time only, which is consistent with how other traffic errors (e.g.,
RevisionMissing) are handled so I'm fine keeping the implementation like this.Release Note