diff options
| author | Jonathan MacMillan <dvorak@google.com> | 2018-06-07 13:21:44 -0700 |
|---|---|---|
| committer | Jonathan MacMillan <dvorak@google.com> | 2018-06-07 13:26:40 -0700 |
| commit | 58de5ce6dd49f04fc160262ad365aab962ab82fa (patch) | |
| tree | 0d389f46d6dcc26f632163d0a575a8801664b794 | |
| parent | 2680dadbc6cf2cb4892eb35e222c6a07d210875c (diff) | |
Follow up to #2220, addressing @csbell's comments.
| -rw-r--r-- | contributors/design-proposals/multicluster/multicluster-reserved-namespaces.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/contributors/design-proposals/multicluster/multicluster-reserved-namespaces.md b/contributors/design-proposals/multicluster/multicluster-reserved-namespaces.md index 821ac43c..0f664cb2 100644 --- a/contributors/design-proposals/multicluster/multicluster-reserved-namespaces.md +++ b/contributors/design-proposals/multicluster/multicluster-reserved-namespaces.md @@ -39,10 +39,12 @@ potentially conventions for namespaces that are replicated between clusters (for example, to support a global cluster list that is replicated to all clusters that are contained in the list). -## Conventions for reserved namesp[aces +## Conventions for reserved namespaces By convention, resources in these namespaces are local to the clusters in which -they exist and will not be replicated to other clusters. +they exist and will not be replicated to other clusters. In other words, these +namespaces are private to the clusters they are in, and multicluster operations +must not replicate them or their resources into other clusters. [1] Tools are by no means compelled to look in this namespace for clusters, and can choose to reference Cluster objects from other namespaces as is suitable to |