summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeremy Olmsted-Thompson <jeremyot@google.com>2020-04-20 14:55:09 -0700
committerJeremy Olmsted-Thompson <jeremyot@google.com>2020-04-20 15:03:06 -0700
commitdd4c8b704ef1c9c3bfd928c6fa9234276d61ad18 (patch)
tree072e5655a9e8ede3de0b828525a34b0a9c04b0cf
parentf80df140d60bf54c5880bf5cfce326d5ae70cd38 (diff)
Change ns-sameness position statement to RELEASED
Follows the example of https://github.com/kubernetes/community/blob/master/sig-api-machinery/api-extensions-position-statement.md Also fixes a typo
-rw-r--r--sig-multicluster/namespace-sameness-position-statement.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/sig-multicluster/namespace-sameness-position-statement.md b/sig-multicluster/namespace-sameness-position-statement.md
index 11fdfc52..109ac2e7 100644
--- a/sig-multicluster/namespace-sameness-position-statement.md
+++ b/sig-multicluster/namespace-sameness-position-statement.md
@@ -1,8 +1,8 @@
# Namespace Sameness - SIG Multicluster Position Statement
Author: Jeremy Olmsted-Thompson (**[@jeremyot](https://github.com/jeremyot)**), Google
-Last Edit: 2020/03/24
-Status: IN REVIEW
+Last Edit: 2020/04/20
+Status: RELEASED
## Goal
To establish a normative statement for multi-cluster namespace semantics and
@@ -65,7 +65,7 @@ called "database" in cluster A, no other team may request a namespace called
### Example 2: RBAC sync
Consider the same organization from example 1. As with many large-sized
-organizations, they alreadyhave a central LDAP server which stores policies
+organizations, they already have a central LDAP server which stores policies
about who is supposed to be able to access what systems. They enforce this by
converting those policies into Kubernetes RBAC rules and pushing them down into
their clusters.