Memory leak on not closed clients

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Using latest (4384) version of the Kubernetes plugin we observed memory leak on the Jenkins. Analyzing heap dump found that it is caused by Kubernetes clients that were marked as expired but were never closed.

      From comments of other people it seems to be cause by this change:

      https://github.com/jenkinsci/kubernetes-plugin/pull/1747

       

      logs from KubernetesClientProvider: (Closing expired client log is never present)

      Nov 04, 2025 1:03:31 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider
Expiring Kubernetes client mycluster io.fabric8.kubernetes.client.impl.KubernetesClientImpl@2d6bac84: EXPIRED
Nov 04, 2025 1:03:31 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider
Created new Kubernetes client: mycluster io.fabric8.kubernetes.client.impl.KubernetesClientImpl@77b7e74d
Nov 04, 2025 1:15:42 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider
Expiring Kubernetes client mycluster io.fabric8.kubernetes.client.impl.KubernetesClientImpl@77b7e74d: EXPIRED
Nov 04, 2025 1:15:43 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider
Created new Kubernetes client: mycluster io.fabric8.kubernetes.client.impl.KubernetesClientImpl@40538e0c
Nov 04, 2025 1:41:12 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider
Expiring Kubernetes client mycluster io.fabric8.kubernetes.client.impl.KubernetesClientImpl@40538e0c: EXPIRED
Nov 04, 2025 1:41:13 PM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider
Created new Kubernetes client: mycluster io.fabric8.kubernetes.client.impl.KubernetesClientImpl@29bdc093

            Assignee:
            Unassigned
            Reporter:
            Krzysztof
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: