-
Notifications
You must be signed in to change notification settings - Fork 276
Conversation
Will also address setting Permissive to TCP proxy, we do have some drawbacks to take care of. |
Fixes for CI/demo expected values will need to be addressed |
5602330
to
e317813
Compare
Codecov Report
@@ Coverage Diff @@
## main #1725 +/- ##
==========================================
- Coverage 57.28% 53.40% -3.88%
==========================================
Files 118 124 +6
Lines 5436 5065 -371
==========================================
- Hits 3114 2705 -409
- Misses 2319 2357 +38
Partials 3 3
Continue to review full report at Codecov.
|
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 overall. I'll pull this change and test it.
return nil, err | ||
} | ||
|
||
// Transform into set, when listing apex services we might face repetitions |
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.
Maybe use a mapset instead.
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.
mapset is a map underneath, I imagine you want it for readability at this point; I personally dislike adding deps if not strictly needed - more so if those are not golang official packages
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.
for readability and helpers it provides. We already use it across the code.
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.
I know, and I never liked it. Want me to change it here though? I'm ok with either in any case
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.
not necessarily for this PR but in a follow-up would be good.
d5e536b
to
135057c
Compare
Introduces per-destination filter-chain matching on outbound. This change will allow setting specific L4 or L7 filtering, precursor for TCP routing. - Since we are filtering all permitted traffic, we can generalize the remaining traffic and simplify Egress, which will not require a CIDR anymore. (TODO: cleanup CIDR flags/code) - Since we can match all destination traffic, Permissive mode can now use TCP proxy (instead of wildcarded RDS) to allow also L4 protocols between services. - Additional work that might benefit from it: per-service route table on RDS, TCP routing, .... Additionally: - Fixing the listener tests required adding the long-awaited catalog mock. Will add more tests in subsequent commits.
Co-authored-by: Sneha Chhabria <snchh@microsoft.com>
3171c3a
a6c478e
to
3171c3a
Compare
Introduces per-destination filter-chain matching on outbound
This change will allow setting specific network filtering on per service
destination, which enables finer configuration per-service level,
as well as the use of different network filters to allow not only L7 traffic
through.
Additional benefits:
any remaining traffic as Egress (when enabled), which simplifies
Egress
to not need a CIDR anymore. (TODO: cleanup CIDR flags/code)
on RDS, TCP routing, ....
Additionally:
Fixing the listener tests required adding the long-awaited catalog mock.
Will add more tests in subsequent commits.
New Functionality [X]
Control Plane [X]
Networking [X]
SMI Policy [X]
Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
No