-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Kubernetes: 1.22.4 (Docker Desktop: 4.3.2 - WSL2)
Jenkins: 2.319.1 (Deployed in Kubernetes using open-source helm chart)
Kubernetes-Plugin: 1.31.1
Behind corporate proxy
-
-
kubernetes 1.31.2
Latest version of kubernetes-client-api: 5.11.1-179.v12037658df90 dependency breaks Kubernetes plugin.
When running Jenkinsfile pipeline and using container('name') syntax, fails to exec into separate container. Errors with:
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
Jenkins server logs say something different (actual error):
java.lang.NoSuchMethodError: 'okhttp3.OkHttpClient io.fabric8.kubernetes.client.HttpClientAware.getHttpClient()'
Using yamlFile and Multibranch pipeline.
- causes
-
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
- Closed
- is duplicated by
-
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
- Closed
-
JENKINS-67474 Pipeline is failing due to io.fabric8.kubernetes.client.KubernetesClientException: not ready after n milliseconds
- Closed