Move topic to Configuration section. (#3620)

* Move topic to Configuration section. * Move included file.
2017-05-03 11:10:07 -07:00
parent f28c8376e0
commit 2442dc292f
3 changed files with 5 additions and 2 deletions
@@ -1,81 +0,0 @@
---
-title: Assigning Pods to Nodes
---
-
-{% capture overview %}
-This page shows how to assign a Kubernetes Pod to a particular node in a
-Kubernetes cluster.
-{% endcapture %}
-
-{% capture prerequisites %}
-
-{% include task-tutorial-prereqs.md %}
-
-{% endcapture %}
-
-{% capture steps %}
-
-## Adding a label to a node
-
-1. List the nodes in your cluster:
-
-        kubectl get nodes
-
-    The output is similar to this:
-
-        NAME      STATUS    AGE     VERSION
-        worker0   Ready     1d      v1.6.0+fff5156
-        worker1   Ready     1d      v1.6.0+fff5156
-        worker2   Ready     1d      v1.6.0+fff5156
-
-1. Chose one of your nodes, and add a label to it:
-
-        kubectl label nodes <your-node-name> disktype=ssd
-
-    where `<your-node-name>` is the name of your chosen node.
-
-1. Verify that your chosen node has a `disktype=ssd` label:
-
-        kubectl get nodes --show-labels
-
-
-    The output is similar to this:
-
-        NAME      STATUS    AGE     VERSION            LABELS
-        worker0   Ready     1d      v1.6.0+fff5156     ...,disktype=ssd,kubernetes.io/hostname=worker0
-        worker1   Ready     1d      v1.6.0+fff5156     ...,kubernetes.io/hostname=worker1
-        worker2   Ready     1d      v1.6.0+fff5156     ...,kubernetes.io/hostname=worker2
-
-    In the preceding output, you can see that the `worker0` node has a
-    `disktype=ssd` label.
-
-## Creating a pod that gets scheduled to your chosen node
-
-This pod configuration file describes a pod that has a node selector,
-`disktype: ssd`. This means that the pod will get scheduled on a node that has
-a `disktype=ssd` label.
-
-{% include code.html language="yaml" file="pod.yaml" ghlink="/docs/tasks/administer-cluster/pod.yaml" %}
-
-1. Use the configuration file to create a pod that will get scheduled on your
-   chosen node:
-
-        kubectl create -f http://k8s.io/docs/tasks/administer-cluster/pod.yaml
-
-1. Verify that the pod is running on your chosen node:
-
-        kubectl get pods --output=wide
-
-    The output is similar to this:
-
-        NAME     READY     STATUS    RESTARTS   AGE    IP           NODE
-        nginx    1/1       Running   0          13s    10.200.0.4   worker0
-
-{% endcapture %}
-
-{% capture whatsnext %}
-Learn more about
-[labels and selectors](/docs/user-guide/labels/).
-{% endcapture %}
-
-{% include templates/task.md %}
@@ -1,13 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    env: test
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    imagePullPolicy: IfNotPresent
-  nodeSelector:
-    disktype: ssd