openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OCPBUGS55692: Node description does not match OpenShift configuration

Browse Source
This commit is contained in:
Michael Burke
2025-07-11 10:12:36 -04:00
committed by openshift-cherrypick-robot
parent 388431ce21
commit f88548f36b
2 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
nodes/index.adoc
View File

@@ -38,12 +38,10 @@ Using the OpenShift CLI (`oc`) or the web console, you can perform the following
The following components of a node are responsible for maintaining the running of pods and providing the Kubernetes runtime environment.
Container runtime:: The container runtime is responsible for running containers. Kubernetes offers several runtimes such as containerd, cri-o, rktlet, and Docker.
Container runtime:: The container runtime is responsible for running containers. {product-title} deploys the CRI-O container runtime on each of the {op-system-first} nodes in your cluster. The Windows Machine Config Operator (WMCO) deploys the containerd runtime on its Windows nodes.
Kubelet:: Kubelet runs on nodes and reads the container manifests. It ensures that the defined containers have started and are running. The kubelet process maintains the state of work and the node server. Kubelet manages network rules and port forwarding. The kubelet manages containers that are created by Kubernetes only.
Kube-proxy:: Kube-proxy runs on every node in the cluster and maintains the network traffic between the Kubernetes resources. A Kube-proxy ensures that the networking environment is isolated and accessible.
DNS:: Cluster DNS is a DNS server which serves DNS records for Kubernetes services. Containers started by Kubernetes automatically include this DNS server in their DNS searches.
ifndef::openshift-rosa-hcp[]
@@ -281,4 +279,4 @@ Indicates that the pod is allowed (but not required) to be scheduled on nodes or
[id="commonterms-node-taint"]
Taint::
A core object that comprises a key, value, and effect. Taints and tolerations work together to ensure that pods are not scheduled on irrelevant nodes.
A core object that comprises a key, value, and effect. Taints and tolerations work together to ensure that pods are not scheduled on irrelevant nodes.