smi-spec
smi-spec copied to clipboard
Service Mesh Interface
We came across this paragraph in the traffic split spec while working on OSM and think it might warrant some clarification: > The resource is associated with a root service....
**Describe the proposal** Support custom authorization filter to allow delegating authorization logic to a third party component **Scope** - [ ] New specification - [x] Traffic Access Control - [...
What is the expected behavior when multiple traffic split resources refer to the same apex service? For example, given an _apex_ service: ```yaml --- apiVersion: split.smi-spec.io/v1alpha1 kind: TrafficSplit metadata: name:...
This addresses #132 for the traffic-metrics API. We define an OpenAPI 3.0.0 specification for the traffic metrics API. This formalizes the description of the API given in `traffic-metrics.md`. I tested...
Some resources may break down their traffic metrics into logical groupings of requests called routes. For example, a web application might break down metrics by request path. If the `route`...
Opening this issue to track discussion raised by @grampelberg in #2 > How should this interact with namespaces? One of the downsides to the current workflow is that deployment names...
**Describe the proposal** Add a diagram to this repo of how SMI works in a Kubernetes environment (with adapters) and the state of any/all current adapters. **Scope** - [ ]...
Hi, I am looking forward to the next release of the smi-spec which includes support for TCP routes, via the traffic-specs and traffic-access specs. When is this scheduled to be...
**Describe the proposal** Currently, when an SMI spec API is released, the CRD manifests tracked in https://github.com/servicemeshinterface/smi-sdk-go/tree/master/crds are not made available as a charts as part of the release. This...
In my option the service mesh interface should include ingress and egress specifications of how north/south traffic flows into/out of the mesh. I propose for SMI to adopt [Kubernetes Ingress...