-
Bug
-
Resolution: Fixed
-
Critical
Kubernetes-Nodes seems to be offline because the remoting version is too old but this is not the truth.
In the figure you can see that the top nodes (docker nodes) return 3 digits in the remoting version. The nodes of type k8 (Kubernetes) only return 2 digits. This leads to the assumption that the remoting version is too old.
The difference in the nodes is that the upper ones launched as docker nodes. These are launched via the JNLP launcher. The nodes runs onPrem.
The k8 nodes will be launched via KubernetesLauncher, e. g.
This causes the node to appear offline.
We use Jenkins in Version 2.346.2 The problem also occurs in the version 2.346.3. We use the same base image as the k8 nodes for the docker nodes which are showing the 3-digit remoting version. The image is jenkins/inbound-agent:4.13-2
The versions of the plugins that may be related to it are the following:
kubernetes:3690.va_9ddf6635481
pipeline-model-api:2.2114.v2654ca_721309
pipeline-model-extensions:2.2114.v2654ca_721309
workflow-api:1192.v2d0deb_19d212
workflow-cps:2759.v87459c4eea_ca_
workflow-durable-task-step:1199.v02b_9244f8064
workflow-step-api:639.v6eca_cd8c04a_a_