feat(translator): support switching between service/clusterIP routing#3543
feat(translator): support switching between service/clusterIP routing#3543arkodg merged 21 commits intoenvoyproxy:mainfrom
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3543 +/- ##
==========================================
+ Coverage 68.17% 68.19% +0.02%
==========================================
Files 168 168
Lines 20484 20496 +12
==========================================
+ Hits 13964 13977 +13
+ Misses 5511 5510 -1
Partials 1009 1009 ☔ View full report in Codecov by Sentry. |
|
thanks for picking this one up @evacchi ! enabling service routing should be make it easier to integrate with service meshes |
47c0d67 to
a03c362
Compare
internal/gatewayapi/testdata/envoyproxy-endpoint-routing-disabled.in.yaml
Outdated
Show resolved
Hide resolved
0bd31a7 to
bf4a29d
Compare
|
hey you also want to copy over the value into the translator here |
internal/gatewayapi/testdata/envoyproxy-endpoint-routing.out.yaml
Outdated
Show resolved
Hide resolved
8e0dab3 to
5e68be5
Compare
internal/gatewayapi/testdata/routingpolicy/envoyproxy-service-routing.out.yaml
Outdated
Show resolved
Hide resolved
|
hey @evacchi one more hiccup, hopefully last one, there's a another PR #3532 that is adding support for reconciling multiple I suggest deleting gateway/internal/gatewayapi/route.go Line 193 in e866ec1 this will also eliminate the need to have a separate test function, and you'll be able to reuse the same one Once this PR is in, #3532 can modify and pass the right |
|
@arkodg wouldn't that flip back the default here to false? I will inject an empty EnvoyProxy (not a default Envoy proxy) and propagate the changes, let me know if that makes sense. I have also renamed |
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
Signed-off-by: Edoardo Vacchi <[email protected]>
26db93d to
23826e1
Compare
|
failed tests are just timing out |
kicked the CI, you can also comment on the GH issue with |
This PR surfaces the internal
EndpointRoutingDisabledflag to theEnvoyProxyspec. This is still missing an e2e test, opening as draft to double-check.The flag defaults to true as it is currently set internally. It might make sense to flip the name toClusterIPRoutingEnabled(so that the default is, perhaps less surprisingly, "false")The new config option is called
routingTypeand it can be set toServiceorCluster.Fixes #1900