-
Notifications
You must be signed in to change notification settings - Fork 514
feat: support listener/routes in post translate hook level #6524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6524 +/- ##
==========================================
+ Coverage 71.05% 71.09% +0.03%
==========================================
Files 220 220
Lines 37892 37965 +73
==========================================
+ Hits 26926 26990 +64
- Misses 9393 9399 +6
- Partials 1573 1576 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me but maybe leave a TODO about subsetting the resources (e.g. selecting clusters by labels etc) sent via PostTranslateModify since the request/response will be potentially a few mb-tens of mb ?
new approach has been tested in envoyproxy/ai-gateway@03573fd and it worked well.
|
3da1ad6
to
94bd9c7
Compare
api/v1alpha1/envoygateway_types.go
Outdated
@@ -576,6 +576,15 @@ type ExtensionManager struct { | |||
type ExtensionHooks struct { | |||
// XDSTranslator defines all the supported extension hooks for the xds-translator runner | |||
XDSTranslator *XDSTranslatorHooks `json:"xdsTranslator,omitempty"` | |||
|
|||
// EnablePostTranslateListenersAndRoutes controls whether listeners and routes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my preference would be to have something like
resource:
listener:
selector: {}
which selects all listeners, these key values are based on resource metadata
or some form with a selector, so we can only send specific resources
- should the top level be
resource
ortranslationHook
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wdyt @guydc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created an issue for track: #6539
Signed-off-by: bitliu <[email protected]>
Signed-off-by: bitliu <[email protected]>
Signed-off-by: bitliu <[email protected]>
Signed-off-by: bitliu <[email protected]>
thanks @Xunzhuo, prefer
|
should add a stage in it? Like |
yeah we could add that and extend it in the future, afaik most users are using |
Signed-off-by: bitliu <[email protected]>
Signed-off-by: bitliu <[email protected]>
Signed-off-by: bitliu <[email protected]>
Signed-off-by: bitliu <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Thanks for adding this!
/retest |
What type of PR is this?
feat: support listener/routes in post translate hook level
Which issue(s) this PR fixes:
Fixes #6523
Release Notes: Yes