You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.
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 Kubernetes clusters as well as to support services running outside a Kubernetes cluster such as on VMs.
The proposal led to a debate, revolving around the notion of authorization within the SMI policy, namely, how does the service mesh implementation determine whether the access that is specified between two services within the policy is valid, and given its validity how does the service mesh enforce this access?
Creating this issue to track the discussion.
The text was updated successfully, but these errors were encountered:
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 Kubernetes clusters as well as to support services running outside a Kubernetes cluster such as on VMs.
The proposal led to a debate, revolving around the notion of authorization within the SMI policy, namely, how does the service mesh implementation determine whether the access that is specified between two services within the policy is valid, and given its validity how does the service mesh enforce this access?
Creating this issue to track the discussion.
The text was updated successfully, but these errors were encountered: