smi-spec
smi-spec copied to clipboard
servicemeshinterface
Service Mesh Interface
We require CNCF projects to go through this badging process: https://bestpractices.coreinfrastructure.org/en This will involve crafting a SECURITY.md too
We need to ensure we don't still have go package references that call out to deislabs orgs.
Include: - Who we serve (application integrators, eg. Kiali and Flagger) - Application integration - Tooling integration - LCD service mesh definition - List integrations and implementations - Version information...
https://docs.google.com/document/d/1NTBaJf6LhUBlF8_lfvBBt_MbyPvT-6CZNg6Ckpm_yCo/edit#heading=h.wpaq1r94m39s
Great to see header filters added to the SMI spec! I had a question, which I don't think has been addressed so far (apologies if I missed it)... Take, for...
I've recently discovered SMI and have enjoyed digging into the specs. I'm hoping to kickoff a discussion on how we should be thinking about defining new L7 protocols, to make...
In an ongoing PR #67 there has been consensus in re-defining the notion of a service within the context of an SMI policy to allow SMI spec to support multiple...
Currently the traffic targets define access control rules along a set of routes between a source and destination (https://github.com/deislabs/smi-spec/blob/master/traffic-access-control.md). Since we are trying to define rules such as "A can...
Take the example definition in the Traffic Access Control page: ``` --- kind: TrafficTarget apiVersion: access.smi-spec.io/v1alpha1 metadata: name: path-specific namespace: default destination: kind: ServiceAccount name: service-a namespace: default port: 8080...
