kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Jeremy Olmsted-Thompson 2020-04-20 14:55:09 -07:00
parent f80df140d6
commit dd4c8b704e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
sig-multicluster/namespace-sameness-position-statement.md
View File

@ -1,8 +1,8 @@
# Namespace Sameness - SIG Multicluster Position Statement # Namespace Sameness - SIG Multicluster Position Statement
Author: Jeremy Olmsted-Thompson (**[@jeremyot](https://github.com/jeremyot)**), Google Author: Jeremy Olmsted-Thompson (**[@jeremyot](https://github.com/jeremyot)**), Google
Last Edit: 2020/03/24 Last Edit: 2020/04/20
Status: IN REVIEW Status: RELEASED
## Goal ## Goal
To establish a normative statement for multi-cluster namespace semantics and 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 ### Example 2: RBAC sync
Consider the same organization from example 1. As with many large-sized 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 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 converting those policies into Kubernetes RBAC rules and pushing them down into
their clusters. their clusters.