-
Notifications
You must be signed in to change notification settings - Fork 335
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
feat(kuma-cp) initial gateway TrafficRoute support #2547
feat(kuma-cp) initial gateway TrafficRoute support #2547
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2547 +/- ##
==========================================
+ Coverage 52.25% 52.45% +0.19%
==========================================
Files 865 872 +7
Lines 49300 49662 +362
==========================================
+ Hits 25761 26049 +288
- Misses 21453 21510 +57
- Partials 2086 2103 +17
Continue to review full report at Codecov.
|
Add support for binding TrafficRoute resources to Gateways. This is based on outbound proxy generator code, but there are still a number of missing features and outstanding TODO items. It is possible to configure simple HTTP Gateway use cases and forward traffic to Kuma services as long as the mesh is not configures with mTLS. A Gateway can have more than one TrafficRoute resource bound, and this works correctly by merging the routes in match order. Signed-off-by: James Peach <james.peach@konghq.com>
Signed-off-by: James Peach <james.peach@konghq.com>
@lobkovilya sorry about the force push, my working copy was a bit behind my fork :-( |
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.
There are lots of todos but as a concept, we are heading in a good direction.
Signed-off-by: James Peach <james.peach@konghq.com>
I've addresses all the review feedback so far. Thanks! |
Add support for binding TrafficRoute resources to Gateways. This is based on outbound proxy generator code, but there are still a number of missing features and outstanding TODO items. It is possible to configure simple HTTP Gateway use cases and forward traffic to Kuma services as long as the mesh is not configures with mTLS. A Gateway can have more than one TrafficRoute resource bound, and this works correctly by merging the routes in match order. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit d5af0df)
Add support for binding TrafficRoute resources to Gateways. This is based on outbound proxy generator code, but there are still a number of missing features and outstanding TODO items. It is possible to configure simple HTTP Gateway use cases and forward traffic to Kuma services as long as the mesh is not configures with mTLS. A Gateway can have more than one TrafficRoute resource bound, and this works correctly by merging the routes in match order. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit d5af0df) Co-authored-by: James Peach <james.peach@konghq.com>
Add support for binding TrafficRoute resources to Gateways. This is based on outbound proxy generator code, but there are still a number of missing features and outstanding TODO items. It is possible to configure simple HTTP Gateway use cases and forward traffic to Kuma services as long as the mesh is not configures with mTLS. A Gateway can have more than one TrafficRoute resource bound, and this works correctly by merging the routes in match order. Signed-off-by: James Peach <james.peach@konghq.com>
Add support for binding TrafficRoute resources to Gateways. This is based on outbound proxy generator code, but there are still a number of missing features and outstanding TODO items. It is possible to configure simple HTTP Gateway use cases and forward traffic to Kuma services as long as the mesh is not configures with mTLS. A Gateway can have more than one TrafficRoute resource bound, and this works correctly by merging the routes in match order. Signed-off-by: James Peach <james.peach@konghq.com>
Summary
Add support for binding TrafficRoute resources to Gateways. This is
based on outbound proxy generator code, but there are still a number of
missing features and outstanding TODO items.
It is possible to configure simple HTTP Gateway use cases and forward
traffic to Kuma services as long as the mesh is not configures with mTLS.
A Gateway can have more than one TrafficRoute resource bound, and this
works correctly by merging the routes in match order.
Full changelog
N/A
Issues resolved
N/A
Documentation
N/A
Testing
Backwards compatibility
backport-to-stable
label if the code is backwards compatible. Otherwise, list breaking changes.