Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67484

Kubernetes plugin stopped working - Timed out waiting for websocket connection. You should increase the value of system property org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout currently set at 30 seconds

XMLWordPrintable

      My SQL query pipelines stopped working without any reason with error:

      Timed out waiting for websocket connection. You should increase the value of system property org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout currently set at 30 seconds

      I'm using Jenkins CI installed with Helm Chart, so I tried to set the system property in the values.yaml file as suggested here  but it didn't work, I'm still getting the same error.

      This is how my values file looks like:

      javaOpts: "-Dproperty=org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout=300" 
jenkinsOpts: "-Dproperty=org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout=300"

       I can see that some people already talked about this problem, but solution is not clear for me JENKINS-56939.

      Using latest Kubernetes plugin version: 1.31.1

          [JENKINS-67484] Kubernetes plugin stopped working - Timed out waiting for websocket connection. You should increase the value of system property org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout currently set at 30 seconds

          Jonathan Rogers added a comment -

          I had the exact same problem starting a couple of days ago, so I downgraded things that had been upgraded just before that. For me, the problem seems to be with the kubernetes-client-api plugin. The most recent version (5.11.1-179.v12037658df90) does not work. The previous version works: 5.10.1-171.vaa0774fb8c20

          Jonathan Rogers added a comment - I had the exact same problem starting a couple of days ago, so I downgraded things that had been upgraded just before that. For me, the problem seems to be with the kubernetes-client-api plugin. The most recent version (5.11.1-179.v12037658df90) does not work. The previous version works: 5.10.1-171.vaa0774fb8c20

          Morten Birkelund added a comment - - edited

          jrogers thanks for sharing. Downgrading solved it for me aswell

          Morten Birkelund added a comment - - edited jrogers thanks for sharing. Downgrading solved it for me aswell

          Oliver Grad added a comment -

          Hi,

          we've run into the same issue since we've installed Kubernetes-Plugin: 1.31.1 yesterday morning.

          Some minutes ago we upgraded to Kubernetes-Plugin: 1.31.2 and the problem is solved for us.

          Oliver Grad added a comment - Hi, we've run into the same issue since we've installed Kubernetes-Plugin: 1.31.1 yesterday morning. Some minutes ago we upgraded to Kubernetes-Plugin: 1.31.2 and the problem is solved for us.

            Unassigned Unassigned
            lungosta Luis Ocampo
            Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: