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

JNLP slave pod gets created even when a different slave is configured

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • kubernetes-plugin
    • None
    • kubernetes 1.51, coreos, kubernetes plugin 0.10

      plugin 0.10... I have a kubernetes pod template configured with a different slave image than the default JNLP slave template. For some reason when I look at pods for my slave nodes I now see both the jenkinsci/jnlp-slave:alpine container and my intended container:

      jenkins-docker-dood-slave
      Image:
      pswenson/jenkins-docker-dood-slave:2.0

      This causes big problems as the jobs almost always go to the JNLP slave instead of the jenkins-docker-dood-slave and this causes a job failure (my custom slave image runs docker commands and uses a shared docker socket)

      The old 0.8 version didn't have this problem, however that version doesn't appear to work with kube 1.51.

      I'm going to look at the source code of the plugin and see if I can figure out what's going on. Any suggestions would be greatly appreciated.

            csanchez Carlos Sanchez
            philswenson phil swenson
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: