whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #6876 from stewart-yu/patch-1

Browse Source 
Update namespaces.md
This commit is contained in:
Qiming
2018-01-09 13:29:27 +08:00
committed by GitHub
parent 96648cfc1d c976aa8960
commit 0812f2a783
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-cluster/namespaces-walkthrough.md
+3 -3
View File
@@ -53,20 +53,20 @@ One pattern this organization could follow is to partition the Kubernetes cluste
Let's create two new namespaces to hold our work. Let's create two new namespaces to hold our work.
Use the file [`namespace-dev.json`](/docs/admin/namespaces/namespace-dev.json) which describes a development namespace: Use the file [`namespace-dev.json`](/docs/tasks/administer-cluster/namespace-dev.json) which describes a development namespace:
{% include code.html language="json" file="namespace-dev.json" ghlink="/docs/tasks/administer-cluster/namespace-dev.json" %} {% include code.html language="json" file="namespace-dev.json" ghlink="/docs/tasks/administer-cluster/namespace-dev.json" %}
Create the development namespace using kubectl. Create the development namespace using kubectl.
```shell ```shell
$ kubectl create -f docs/admin/namespaces/namespace-dev.json $ kubectl create -f https://k8s.io/docs/tasks/administer-cluster/namespace-dev.json
``` ```
And then let's create the production namespace using kubectl. And then let's create the production namespace using kubectl.
```shell ```shell
$ kubectl create -f docs/tasks/administer-cluster/namespace-prod.json $ kubectl create -f https://k8s.io/docs/tasks/administer-cluster/namespace-prod.json
``` ```
To be sure things are right, let's list all of the namespaces in our cluster. To be sure things are right, let's list all of the namespaces in our cluster.
docs/tasks/administer-cluster/namespaces.md
+3 -3
View File
@@ -139,14 +139,14 @@ One pattern this organization could follow is to partition the Kubernetes cluste
Let's create two new namespaces to hold our work. Let's create two new namespaces to hold our work.
Use the file [`namespace-dev.json`](/docs/admin/namespaces/namespace-dev.json) which describes a development namespace: Use the file [`namespace-dev.json`](/docs/tasks/administer-cluster/namespace-dev.json) which describes a development namespace:
{% include code.html language="json" file="namespace-dev.json" ghlink="/docs/admin/namespaces/namespace-dev.json" %} {% include code.html language="json" file="namespace-dev.json" ghlink="/docs/tasks/administer-cluster/namespace-dev.json" %}
Create the development namespace using kubectl. Create the development namespace using kubectl.
```shell ```shell
$ kubectl create -f docs/admin/namespaces/namespace-dev.json $ kubectl create -f docs/tasks/administer-cluster/namespace-dev.json
``` ```
And then let's create the production namespace using kubectl. And then let's create the production namespace using kubectl.