EKS Jenkins Kubernetes plugin tcpSlaveAgentListener/: connect timed out

Using Jenkins
1

I have deployed Jenkins on EKS using the helm chart. The Kubernetes plugin is installed and populated with default values. I am getting the below error whenever I run the job.

- jnlp -- terminated (255)
-----Logs-------------
INFO: Using /home/jenkins/agent/remoting as a remoting work directory
Feb 10, 2023 6:32:24 AM org.jenkinsci.remoting.engine.WorkDirManager setupLogging
INFO: Both error and output logs will be printed to /home/jenkins/agent/remoting
Feb 10, 2023 6:32:24 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://jenkins.jenkins.svc.cluster.local:8080/]
Feb 10, 2023 6:32:54 AM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: Failed to connect to http://jenkins.jenkins.svc.cluster.local:8080/tcpSlaveAgentListener/: connect timed out
java.io.IOException: Failed to connect to http://jenkins.jenkins.svc.cluster.local:8080/tcpSlaveAgentListener/: connect timed out
    at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:216)
    at hudson.remoting.Engine.innerRun(Engine.java:751)
    at hudson.remoting.Engine.run(Engine.java:543)
Caused by: java.net.SocketTimeoutException: connect timed out
    at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
    at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
    at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
    at java.base/java.net.Socket.connect(Unknown Source)
    at java.base/sun.net.NetworkClient.doConnect(Unknown Source)
    at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
    at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
    at java.base/sun.net.www.http.HttpClient.<init>(Unknown Source)
    at java.base/sun.net.www.http.HttpClient.New(Unknown Source)
    at java.base/sun.net.www.http.HttpClient.New(Unknown Source)
    at java.base/sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
    at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
    at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
    at java.base/sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
    at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:213)

I have attached network load balncer to EKS. There are three nodes running. Load balncer is marking two instances as unhealthy. Following is the resources deployed in jenkins workspace.

pod/jenkins-0   2/2     Running   0          18m

NAME                    TYPE       CLUSTER-IP       EXTERNAL-IP   PORT(S)           AGE
service/jenkins         NodePort   172.20.30.116    <none>        8080:32080/TCP    18m
service/jenkins-agent   NodePort   172.20.213.212   <none>        50000:32081/TCP   18m

NAME                       READY   AGE
statefulset.apps/jenkins   1/1     18m

Seetings of Kubernetes Plugin:
Kubernetes URL: https://kubernetes.default

image
image1235×802 46.6 KB