-
Notifications
You must be signed in to change notification settings - Fork 125
Clarify: scope includes but is not limited to k8s. #220
Clarify: scope includes but is not limited to k8s. #220
Conversation
Signed-off-by: Bridget Kromhout <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Based on the discussion in today's SMI working group for multi-cluster, we want to clarify that SMI includes but is not limited to Kubernetes.
This changes "a specification for service meshes that run on Kubernetes" to "a specification for service meshes, with a
focus on those that run on Kubernetes".
If we can have maintainers indicate their approval of (or changes to) this PR, that will serve to indicate consensus.
Signed-off-by: Bridget Kromhout [email protected]