Michelle Dhanani
Michelle Dhanani
+1 to resolving this ambiguity In this example, it looks like the TS resource name gets used to describe the deployment strategy and this scenario makes it seem that there...
+1 to the validating webhook idea. I'm for only having one traffic split per apex service for traffic split (up to TrafficSplit v1alpha2). Because we have routing based on HTTPRouteGroup...
+1 would love to see an SMI chart be cut as part of the SMI release. It'd be nice to import these as a dependency from within an implementation
Yes! When we're trying to rate limit traffic to particular service or `destination`, it makes sense to specify that information as part of `TrafficTarget` because `TrafficTarget` allows us to define...
Thanks @nicholasjackson and @kumarabd. Thanks for the suggestions. The benefits I see of Nic's version is that there is greater clarity and less room for error when building and validating...
From an implementation perspective, I wonder if it would be better to have a default set of backends or remove the option of the default backends and only apply backends...
Looking at this. It shouldn't even break the sdk/Kubernetes API versioning requirements. Do you see any issues @nicholasjackson ?
@johnsonshi Your proposal makes sense to me. 1. We should think about how to handle conflicts between traffic splits that reference the same root service. Should there only be 1...
That would be great. Thank you @patricekrakow
Hey @patricekrakow - option 2 looks the most clear to me. Would you still be able to work on this issue? cc/ @johnsonshi