CODEWITHSUNDEEP
jenkinskubernetesjenkins-pipeline
CptDolphin
CptDolphin

Reputation: 474

kubernetes jenkins slave doesnt see master

I'm deploying Jenkins with helm charts to GKE and having issue with jobs, mainly the slave doesn't see tcpSlaveAgentListener - it happens whenever i start any job - the master triggers scale of new jenkins-agent but it terminates with error like these

SEVERE: Failed to connect to http://jenkins.jenkins.svc.my_website:8080/tcpSlaveAgentListener/: jenkins.jenkins.svc.my_website
java.io.IOException: Failed to connect to http://jenkins.jenkins.svc.my_website:8080/tcpSlaveAgentListener/: jenkins.jenkins.svc.my_website
  at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:206)

I replaced my domain(like google.com) to my_website - I'm curious about the jenkins.jenkins.svc.my_domain - is it built in or do I have some duplicates somewhere? that it has so many subdomains ?

Upvotes: 0

Views: 1582

Answers (2)

Pankaj Saini
Pankaj Saini

Reputation: 1648

The slave connects back to Jenkins via JNLP on JNLP port (TCP port for incoming agents). If you will go to Manage > Configure Global Security; you would be able to see that; select Fixed port and specify a value say 50000.

You can also use tunnel under kubernetes plugin config (Manage> configure system) and specify jenkins.jenkins.svc:50000. (if your namespace is jenkins and serive exposed name is jenkins too)

Upvotes: 1

Subramanian Manickam
Subramanian Manickam

Reputation: 1349

You have to configure TCP port for incoming agents to 50000 on master Jenkins configure section. 

1. Go to Configure Global Security
2. Under Agents section, select Fixed option and keep 50000 value.

Upvotes: 3

Related Questions