Administering Cluters section; Edit This Page funcitonality

This commit is contained in:
John Mulhausen
2016-02-11 02:15:49 -08:00
parent 5a960ec8e7
commit f782b2e0fb
439 changed files with 156 additions and 86841 deletions
+2 -21
View File
@@ -1,13 +1,7 @@
---
layout: docwithnav
title: "Kubernetes Namespaces"
section: guides
---
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
## Kubernetes Namespaces
Kubernetes _[namespaces](../../../docs/admin/namespaces.html)_ help different projects, teams, or customers to share a Kubernetes cluster.
@@ -286,17 +280,4 @@ cattle-zz7ea 1/1 Running 0 12s
At this point, it should be clear that the resources users create in one namespace are hidden from the other namespace.
As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different
authorization rules for each namespace.
<!-- BEGIN MUNGE: IS_VERSIONED -->
<!-- TAG IS_VERSIONED -->
<!-- END MUNGE: IS_VERSIONED -->
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/admin/namespaces/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->
authorization rules for each namespace.