smi-spec
smi-spec copied to clipboard
servicemeshinterface
Service Mesh Interface
Right now a typical `TrafficTarget` example looks like following: ```yaml kind: TrafficTarget apiVersion: access.smi-spec.io/v1alpha1 metadata: name: api-service-api namespace: default destination: kind: ServiceAccount name: api-service namespace: default port: 8080 specs: -...
Currently the spec only mentions http. One may want to have different policies for http and https. E.g. block all http and only allow https to pass. Likewise for what...
#26 has got me thinking about documentation for the spec and how to use it as a user. There are definitely best practices emerging as we start in on implementation....
### What problem are you trying to solve? I would like to have policy for things other than access control. In particular, it would be nice to describe policy around...
It is pretty valuable to base HPA decisions off some of the data in `TrafficMetrics`. What is the integration story there? How could implementations be integrated?
Hi 👋 Evaluating service mesh solutions and stumbled upon this spec. Wondered if mirroring / shadowing is planned? That is, duplicating and sending the same traffic to multiple endpoints. Read...
