This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 277
Add SMI Traffic Split (v1alpha4) support in the routes v2 feature #2368
Labels
Milestone
Comments
snehachhabria
changed the title
Add SMI Traffic Split support in the routes v2 feature
Add SMI Traffic Split (v1alpha4) support in the routes v2 feature
Jan 27, 2021
Based on offline discussion this will not be implemented as a part of routesv2 refactor and is an enhancement that will come later. Removing routesv2 label and milestone 0.8 |
michelleN
added
size/L
14 days (~2.5 weeks)
and removed
size/XL
20 days (4 weeks)
labels
Feb 11, 2021
@snehachhabria does this mean that the split upgreade (to v1alpha3 or v1alpha4) won't be include in milestone 0.8? |
@addozhang yes that's right, we will most probably work on this in milestone 0.9 |
michelleN
pushed a commit
to michelleN/osm
that referenced
this issue
Mar 15, 2021
+ updates OSM to support SMI Traffic Split v1alpha4 which includes HTTPRouteGroup support enabling scenarios such as A/B testing and routing based on HTTP attributes * resolves openservicemesh#2759 * resolves openservicemesh#2368 Signed-off-by: Michelle Noorali <minooral@microsoft.com>
michelleN
pushed a commit
to michelleN/osm
that referenced
this issue
Mar 16, 2021
+ updates OSM to support SMI Traffic Split v1alpha4 which includes HTTPRouteGroup support enabling scenarios such as A/B testing and routing based on HTTP attributes * resolves openservicemesh#2759 * resolves openservicemesh#2368 Signed-off-by: Michelle Noorali <minooral@microsoft.com>
michelleN
pushed a commit
to michelleN/osm
that referenced
this issue
Mar 16, 2021
+ updates OSM to support SMI Traffic Split v1alpha4 which includes HTTPRouteGroup support enabling scenarios such as A/B testing and routing based on HTTP attributes * resolves openservicemesh#2759 * resolves openservicemesh#2368 Signed-off-by: Michelle Noorali <minooral@microsoft.com>
michelleN
pushed a commit
to michelleN/osm
that referenced
this issue
Mar 16, 2021
+ updates OSM to support SMI Traffic Split v1alpha4 which includes HTTPRouteGroup support enabling scenarios such as A/B testing and routing based on HTTP attributes * resolves openservicemesh#2759 * resolves openservicemesh#2368 Signed-off-by: Michelle Noorali <minooral@microsoft.com>
michelleN
pushed a commit
to michelleN/osm
that referenced
this issue
Mar 16, 2021
+ now accepts a slice of service.WeightedCluster + easier to create RouteWeightedCluster now where there is more than one backend/weighted cluster + prep for openservicemesh#2368 Signed-off-by: Michelle Noorali <minooral@microsoft.com>
michelleN
pushed a commit
to michelleN/osm
that referenced
this issue
Mar 16, 2021
+ updates OSM to support SMI Traffic Split v1alpha4 which includes HTTPRouteGroup support enabling scenarios such as A/B testing and routing based on HTTP attributes * resolves openservicemesh#2759 * resolves openservicemesh#2368 Signed-off-by: Michelle Noorali <minooral@microsoft.com>
This issue will be closed due to a long period of inactivity. If you would like this issue to remain open then please comment or update. |
Duplicate of #4880 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
The routes v2 feature is an experimental feature which changes the way we program routes via RDS on the envoy sidecar proxies running next to each application Pod [link to proposal coming]. It currently supports SMI Traffic Access policies. If you enable the feature via the ROUTES_V2 env variable and run this demo, you'll see the once SMI policies are enabled, a source Pod that has been enabled via an SMI Traffic Target object will be able to talk to the destination specified in the policy and a destination will be able to accept requests at certain route configuration (path, method, headers, etc. specified in the SMI TrafficTarget)
This issue is to track the work to support SMI Traffic Split v1alpha4. If an SMI Traffic Split policy is applied, the outbound routes of all relevant client Pod proxies should be updated with the routing configuration specified in the SMI Traffic Split resource.
The text was updated successfully, but these errors were encountered: