From b081edb8958fa25e9151d7ee1482c39dae7dec68 Mon Sep 17 00:00:00 2001 From: Qiming Teng Date: Mon, 25 Dec 2017 14:38:40 +0800 Subject: [PATCH] Remove unnecessary manual node object creation Closes: #2397 --- .../fedora/fedora_manual_config.md | 34 ------------------- 1 file changed, 34 deletions(-) diff --git a/docs/getting-started-guides/fedora/fedora_manual_config.md b/docs/getting-started-guides/fedora/fedora_manual_config.md index 8200465b1c858..6ce8eb357ac90 100644 --- a/docs/getting-started-guides/fedora/fedora_manual_config.md +++ b/docs/getting-started-guides/fedora/fedora_manual_config.md @@ -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.***