Remove unnecessary manual node object creation (#6765)

Closes: #2397
2018-01-26 08:48:36 +08:00
parent c1ef846cce
commit 98d106ef20
1 changed files with 0 additions and 34 deletions
@@ -101,40 +101,6 @@ for SERVICES in etcd kube-apiserver kube-controller-manager kube-scheduler; do
 done
 ```
 * Addition of nodes:
 * Create following node.json file on Kubernetes master node:
 ```json
 {
    "apiVersion": "v1",
    "kind": "Node",
    "metadata": {
        "name": "fed-node",
        "labels":{ "name": "fed-node-label"}
    },
    "spec": {
        "externalID": "fed-node"
    }
 }
 ```
 Now create a node object internally in your Kubernetes cluster by running:
 ```shell
 $ kubectl create -f ./node.json
 $ kubectl get nodes
 NAME            STATUS        AGE      VERSION
 fed-node        Unknown       4h
 ```
 Please note that in the above, it only creates a representation for the node
 _fed-node_ internally. It does not provision the actual _fed-node_. Also, it
 is assumed that _fed-node_ (as specified in `name`) can be resolved and is
 reachable from Kubernetes master node. This guide will discuss how to provision
 a Kubernetes node (fed-node) below.
 **Configure the Kubernetes services on the node.**
 ***We need to configure the kubelet on the node.***