Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove unnecessary manual node object creation #6765

Merged
merged 1 commit into from
Jan 26, 2018
Merged

Remove unnecessary manual node object creation #6765

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 0 additions & 34 deletions docs/getting-started-guides/fedora/fedora_manual_config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.***
Expand Down