OpenShift Node Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 35: | Line 35: | ||
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: | 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: | ||
{{ | {{Internal|OpenShift_3.5_Installation#OpenShift_Node_Configuration|OpenShift 3.5 Installation Procedure - Node Configuration}} | ||
Revision as of 03:40, 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:
Removing a Node
TODO: https://docs.openshift.com/container-platform/3.5/admin_guide/manage_nodes.html#deleting-nodes