I am running a Kubernetes cluster with a Windows node to run my tests on. I have installed the Kubernetes plugin in Jenkins, and when a pod is created in the Windows node it creates the jnlp-slave container in it as well, but the image is Linux based. This fails the pod creation, I looked everywhere for a way to omit the jnlp-slave container or at the very least change it to one that works on Windows from the 'Configure System' section. 

      On that same note is there an official jnlp-slave image for Windows, or is the Linux on the only available? If not this can be added as a choice for the user if they are using windows pods.

      Thanks

          [JENKINS-57256] Kubernetes plugin Windows agent support

          Otavio Moraes created issue -

          There is no support for windows yet

          Carlos Sanchez added a comment - There is no support for windows yet
          Carlos Sanchez made changes -
          Summary Original: JNLP-Slave container failing to start on Windows Node New: Kubernetes plugin Windows agent support

          If you create a container with the name "jnlp" you prevent the default jnlp image from starting - so you can create your own jnlp windows image which takes it place. 

          Raphael Höser added a comment - If you create a container with the name "jnlp" you prevent the default jnlp image from starting - so you can create your own jnlp windows image which takes it place. 

          snapstromegon I guess doing that means that your linux node will not use the correct docker image anyore

          Olivier Vernin added a comment - snapstromegon I guess doing that means that your linux node will not use the correct docker image anyore

          olblak Since you need to create two pods to build on windows and linux you can use two different containers as jnlp containers.

          You create two podTemplates with each a container named jnlp. In the containerTemplate you set the image to thw jnlp image for your platform (on linux you can also not create a jnlp container to use the default, but be aware of inheritance).

          That way you can have a linux and a windows jnlp node in your cluster.

           

          If I didn't understand you correctly and you meant something else with "your linux node will not use the correct docker image anymore" please clarify.

          Raphael Höser added a comment - olblak Since you need to create two pods to build on windows and linux you can use two different containers as jnlp containers. You create two podTemplates with each a container named jnlp. In the containerTemplate you set the image to thw jnlp image for your platform (on linux you can also not create a jnlp container to use the default, but be aware of inheritance). That way you can have a linux and a windows jnlp node in your cluster.   If I didn't understand you correctly and you meant something else with "your linux node will not use the correct docker image anymore" please clarify.

          No indeed you are totally right, two different pods can have different container with the same name and in this case jnlp

          Olivier Vernin added a comment - No indeed you are totally right, two different pods can have different container with the same name and in this case jnlp
          Jesse Glick made changes -
          Labels Original: jnlp-slave kubernetes kubernetes-plugin windows New: jnlp-slave windows
          Jesse Glick made changes -
          Issue Type Original: Improvement [ 4 ] New: New Feature [ 2 ]
          Jesse Glick made changes -
          Assignee Original: Carlos Sanchez [ csanchez ]

            jglick Jesse Glick
            moraesmedacuity Otavio Moraes
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: