OpenShift Node Operations: Difference between revisions
| Line 64: | Line 64: | ||
<font color=red>TODO: https://docs.openshift.com/container-platform/3.5/admin_guide/manage_nodes.html#deleting-nodes</font> | <font color=red>TODO: https://docs.openshift.com/container-platform/3.5/admin_guide/manage_nodes.html#deleting-nodes</font> | ||
=Adding a new Master= | |||
<font color=red>TODO: https://docs.openshift.com/container-platform/3.5/install_config/adding_hosts_to_existing_cluster.html#adding-nodes-advanced</font> | |||
Revision as of 04:08, 18 October 2017
External
Internal
Overview
A node is a Linux container host. More details about nodes are available here:
Getting Information about a Node
oc get nodes oc get node <node-name> oc describe node/<node-name>
Starting/Stopping a Node
Get Labels Applied to a Node
Update Labels on a Node
Other Procedures
Adding a New Node
New nodes can be added with the scaleup.yml playbook. The playbook generates and distributes new certificates for the new hosts, then runs the configuration playbook on the new hosts only. However, before running the playbook, the host must be prepared in the same way the other nodes were. If the nodes were created based on a template, the same template should be used to stand up the new node. For more details, see:
Use the same Ansible inventory file that was used to install the rest of the cluster.
On the Ansible host, update to the latest version of 'atomic-openshift-utils'
yum update atomic-openshift-utils
In the Ansible inventory file, add "new_<host_type> to the [OSEv3:children] section:
[OSEv3:children] masters etcd nodes new_nodes lb nfs
Create a [new_<host_type>] section following the patterns already in place for the similar types of nodes:
[new_nodes]
node3.local openshift_node_labels="{'logging':'true', 'cluster':'noper430', 'env':'lab'}"
Removing a Node
TODO: https://docs.openshift.com/container-platform/3.5/admin_guide/manage_nodes.html#deleting-nodes