whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update cloud controller doc on node controller

Browse Source 
This change updates the information about the node controller in the
cloud controller managers. The node controller is not responsible for
creating new node objects, it updates them with information from the
provider infrastructure.
This commit is contained in:
Michael McCune
2021-11-08 16:07:25 -05:00
parent b7899c1e2d
commit 0d864c18d9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/architecture/cloud-controller.md
+2 -2
View File
@@ -43,11 +43,11 @@ The controllers inside the cloud controller manager include:
### Node controller ### Node controller
The node controller is responsible for creating {{< glossary_tooltip text="Node" term_id="node" >}} objects The node controller is responsible for updating {{< glossary_tooltip text="Node" term_id="node" >}} objects
when new servers are created in your cloud infrastructure. The node controller obtains information about the when new servers are created in your cloud infrastructure. The node controller obtains information about the
hosts running inside your tenancy with the cloud provider. The node controller performs the following functions: hosts running inside your tenancy with the cloud provider. The node controller performs the following functions:
1. Initialize a Node object for each server that the controller discovers through the cloud provider API. 1. Update a Node object with the corresponding server's unique identifier obtained from the cloud provider API.
2. Annotating and labelling the Node object with cloud-specific information, such as the region the node 2. Annotating and labelling the Node object with cloud-specific information, such as the region the node
is deployed into and the resources (CPU, memory, etc) that it has available. is deployed into and the resources (CPU, memory, etc) that it has available.
3. Obtain the node's hostname and network addresses. 3. Obtain the node's hostname and network addresses.