-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
2
-
None
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 273, OSDOCS Sprint 274, OSDOCS Sprint 275, OSDOCS Sprint 276, OSDOCS Sprint 277, OSDOCS Sprint 278, OSDOCS Sprint 279
-
7
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The node description given in [1] seems to be copied from upstream Kubernetes and does not reflect the OpenShift specific configuration: 1- The section about the "Container runtime" refers to several runtimes when there is no choice in OpenShift and only CRI-O is supported. 2- There is a section about Kube-proxy (also shown on the picture below). However as far as I know kube-proxy is not deployed on OpenShift. 3- The picture shows a "Cloud connector" between Kubelet and some "external" cloud. However there is no description of what such Cloud connector represents. [1] https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/nodes/overview-of-nodes#nodes-overview
Version-Release number of selected component (if applicable):
ALSO, added from https://issues.redhat.com/browse/OCPBUGS-63551:
Also From CNO configuration object table:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/networking_operators/cluster-network-operator#nw-operator-cr-cno-object_cluster-network-operator
spec.kubeProxyConfig: The fields for this object specify the kube-proxy configuration. If you are using the OVN-Kubernetes cluster network plugin, the kube-proxy configuration has no effect.
How reproducible:
Steps to Reproduce:
Actual results:
Expected results:
Additional info:
