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

Merge pull request #4731 from JeremyOT/ns-sameness 

Change ns-sameness position statement to RELEASED
This commit is contained in:
Kubernetes Prow Robot 2020-06-01 09:11:56 -07:00 committed by GitHub
parent 2d6b3747e9 dd4c8b704e
commit 3b5f12a8cb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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
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.