valid. The Kubernetes documentation has more information on node management. >>>>>>> openshift/online-3.7-stage
Each node has a kubelet that updates the node as specified by a container manifest, which is a YAML file that describes a pod. The kubelet uses a set of manifests to ensure that its containers are started and that they continue to run.
A container manifest can be provided to a kubelet by:
A file path on the command line that is checked every 20 seconds.
An HTTP endpoint passed on the command line that is checked every 20 seconds.
The kubelet watching an etcd server, such as /registry/hosts/$(hostname -f), and acting on any changes.
The kubelet listening for HTTP and responding to a simple API to submit a new manifest.
=== Service Proxy
Each node also runs a simple network proxy that reflects the services defined in the API on that node. This allows the node to do simple TCP and UDP stream forwarding across a set of back ends.
=== Node Object Definition
The following is an example node object definition in Kubernetes:
apiVersion: v1 (1) kind: Node (2) metadata: creationTimestamp: null labels: (3) kubernetes.io/hostname: node1.example.com name: node1.example.com (4) spec: externalID: node1.example.com (5) status: nodeInfo: bootID: "" containerRuntimeVersion: "" kernelVersion: "" kubeProxyVersion: "" kubeletVersion: "" machineID: "" osImage: "" systemUUID: ""