abonas
abonas
@jpkrohling fyi ^^
> Thanks @abonas for taking time to go through the spec, here is what I could elaborate on: > > > 1. "The resource is associated with a root service"...
> @abonas care to take a swing at getting a list of terms to be defined in the Glossary? And then we could all jump in and clearly define them?...
> * Probably checkout the working example of the `TrafficSplit` Istio implementation here https://github.com/deislabs/smi-adapter-istio/tree/master/docs/smi-trafficsplit and let us know your thoughts, if this still feels cumbersome to you? yes, it is...
If 2 separate services with different names are representing the same microservice (but its different versions), how are they expected to be recognized as versions of the same service? Is...
define root service
indeed, MTLS is missing from the spec, or specifying routes with HTTPS
> Alas, I don't have any good connections, just a ton of respect for the product. @grampelberg thanks for the feedback! Happy to see this.
@jmazzitelli thanks. my feedback is based on the demo where the presented data set and the behavior that you mention here were not demonstrated.
@aetherknight, my expectation would be that option B and option C will work without getting a "no method error", so the user can build those structures in a nice object...