smi-spec
smi-spec copied to clipboard
defining traffic-destination
In August 2019, @nicholasjackson opened a WIP PR https://github.com/servicemeshinterface/smi-spec/pull/60. Given that it has numerous merge conflicts at this point and no recent discussion on the PR, I'm closing the WIP PR in favor of continuing discussion here.
@nicholasjackson said "I am currently defining traffic-destination which is based round Istio's DestinationRule and Consul's Service Resolve"
@grampelberg said "The Istio one looks like a bunch of LB config and the Consul one appears to fill a similar role to k8s services and endpoints"
What ongoing discussion would help us know if something similar should be merged?