• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • kubernetes-plugin
    • None

      Should the workspaceVolume option work for Windows pods?

      I am testing it for a Windows build in k8 which requires a larger workspace however it does not appear to be made available as a workspace, I see the volume attached to the pod but I don't see it available to be used for the Jenkins workspace

      Infra
      Aws EKS 1.22
      jenkins 2.346.2
      WindowsServer2019CoreContainer v1.22.6-eks-7d68063 m6i.2xlarge node
      provisioner ebs.csi.aws.com

       

      Pipeline example

      pipeline {
          agent {
              kubernetes {
                  yaml '''
      apiVersion: v1
      kind: Pod
      spec:
        nodeSelector:
          kubernetes.io/os: windows
        containers:
        - name: jnlp
          image: jenkins/inbound-agent:windowsservercore-ltsc2019
        securityContext:
          fsGroup: 1000
      '''
                  workspaceVolume dynamicPVC(accessModes: 'ReadWriteOnce', requestsSize: '44Gi')
              }
          }
          stages {
              stage('Main') {
                  steps {
                      powershell "Get-PsDrive -PsProvider FileSystem"
                  }
              }
          }
      }
       

      Pipeline output

      Created Pod: kubernetes jenkins-server/test-36-tn533-7srzh-xnpnd
      Agent test-36-tn533-7srzh-xnpnd is provisioned from template test_36-tn533-n6g7m
      ---
      apiVersion: "v1"
      kind: "Pod"
      metadata:
        annotations:
          buildUrl: "http://jenkins-server.jenkins-server.svc.cluster.local:8080/job/test/36/"
          runUrl: "job/test/36/"
        labels:
          jenkins/jenkins-server-jenkins-agent: "true"
          jenkins/label-digest: "d9d3d043585702a3b1b040b55ca46e6a37c188e9"
          jenkins/label: "test_36-tn533"
        name: "test-36-tn533-7srzh-xnpnd"
        namespace: "jenkins-server"
      spec:
        containers:
        - env:
          - name: "JENKINS_SECRET"
            value: "********"
          - name: "JENKINS_TUNNEL"
            value: "jenkins-server-agent.jenkins-server.svc.cluster.local:50000"
          - name: "JENKINS_AGENT_NAME"
            value: "test-36-tn533-7srzh-xnpnd"
          - name: "JENKINS_NAME"
            value: "test-36-tn533-7srzh-xnpnd"
          - name: "JENKINS_AGENT_WORKDIR"
            value: "/home/jenkins/agent"
          - name: "JENKINS_URL"
            value: "http://jenkins-server.jenkins-server.svc.cluster.local:8080/"
          image: "jenkins/inbound-agent:windowsservercore-ltsc2019"
          name: "jnlp"
          resources:
            limits: {}
            requests:
              memory: "256Mi"
              cpu: "100m"
          volumeMounts:
          - mountPath: "/home/jenkins/agent"
            name: "workspace-volume"
            readOnly: false
        nodeSelector:
          kubernetes.io/os: "windows"
        restartPolicy: "Never"
        securityContext:
          fsGroup: 1000
        volumes:
        - name: "workspace-volume"
          persistentVolumeClaim:
            claimName: "pvc-workspace-test-36-tn533-7srzh-xnpnd"
            readOnly: false
          name: "workspace-volume"Running on test-36-tn533-7srzh-xnpnd in /home/jenkins/agent/workspace/test
      [Pipeline] {
      [Pipeline] stage
      [Pipeline] { (Main)
      [Pipeline] powershellName           Used (GB)     Free (GB) Provider      Root                                               CurrentLocation
      ----           ---------     --------- --------      ----                                               ---------------
      C                   0.11         19.76 FileSystem    C:\                                 ...gent\workspace\test
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] }
      [Pipeline] // podTemplate
      [Pipeline] End of Pipeline
      Finished: SUCCESS

      Pod describe

      Name: test-36-tn533-7srzh-xnpnd
      Namespace: jenkins-server
      Priority: 0
      Node: ip-11-11-11-11.ec2.internal/10.10.10.10
      Start Time: Mon, 08 Aug 2022 17:00:01 +0100
      Labels: jenkins/jenkins-server-jenkins-agent=true
      jenkins/label=test_36-tn533
      jenkins/label-digest=09b9348d08dde652250b98eccaabb99dcdb0b55f
      Annotations: buildUrl: http://jenkins-server.jenkins-server.svc.cluster.local:8080/job/test/36/
      kubernetes.io/psp: eks.privileged
      runUrl: job/test/36/
      vpc.amazonaws.com/PrivateIPv4Address: 10.10.10.10
      Status: Running
      IP: 10.10.10.10
      IPs:
      IP: 10.10.10.10
      Containers:
      jnlp:
      Container ID: docker://daa7660ba7866c63dd970f32a5ebf86a95fb19e8054abc7cfcd078e0fcbbfba6
      Image: jenkins/inbound-agent:windowsservercore-ltsc2019
      Image ID: docker-pullable://jenkins/inbound-agent@sha256:4d35b053a2fb96c782c00fba39dfb41fdb8de8b093f92380d7db481cc526ca8d
      Port: <none>
      HostPort: <none>
      State: Running
      Started: Mon, 08Aug202217:00:31+0100
      Ready: True
      RestartCount: 0
      Limits:
      vpc.amazonaws.com/PrivateIPv4Address: 1
      Requests:
      cpu: 100m
      memory: 256Mi
      vpc.amazonaws.com/PrivateIPv4Address: 1
      Environment:
      JENKINS_SECRET: 1
      JENKINS_TUNNEL: jenkins-server-agent.jenkins-server.svc.cluster.local:50000
      JENKINS_AGENT_NAME: test-36-tn533-7srzh-xnpnd
      JENKINS_NAME: test-36-tn533-7srzh-xnpnd
      JENKINS_AGENT_WORKDIR: /home/jenkins/agent
      JENKINS_URL: http://jenkins-server.jenkins-server.svc.cluster.local:8080/
      Mounts:
      /home/jenkins/agent from workspace-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ldzz5 (ro)
      Conditions:
      Type Status
      Initialized True
      Ready True
      ContainersReady True
      PodScheduled True
      Volumes:
      workspace-volume:
      Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaimin the same namespace)
      ClaimName: pvc-workspace-test-36-tn533-7srzh-xnpnd
      ReadOnly: false
      kube-api-access-ldzz5:
      Type: Projected (a volume that contains injected data from multiple sources)
      TokenExpirationSeconds: 3607
      ConfigMapName: kube-root-ca.crt
      ConfigMapOptional: <nil>
      DownwardAPI: true
      QoS Class: Burstable
      Node-Selectors: kubernetes.io/os=windows
      Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
      node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
      vpc.amazonaws.com/PrivateIPv4Address:NoSchedule op=Exists
      Events:
      TypeReasonAgeFrom Message
      -------------------------
      WarningFailedScheduling 7m53s default-scheduler 0/14 nodes are available: 14 persistentvolumeclaim "pvc-workspace-test-36-tn533-7srzh-xnpnd" not found.
      NormalScheduled 7m48s default-scheduler Successfully assigned jenkins-server/test-36-tn533-7srzh-xnpnd to ip-11-11-11-11.ec2.internal
      NormalResourceAllocated 7m48s vpc-resource-controller AllocatedResource vpc.amazonaws.com/PrivateIPv4Address: 10.10.10.10/19 to the pod
      NormalSuccessfulAttachVolume 7m45s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-7b3e65ae-2b30-4480-b977-8ed782923d5c"
      NormalPulled 7m19s kubelet Container image "jenkins/inbound-agent:windowsservercore-ltsc2019" already present on machine
      NormalCreated 7m19s kubelet Created container jnlp
      NormalStarted 7m18s kubelet Started container jnlp 

          [JENKINS-69285] Kubernetes agent windows pod workspaceVolume

          There are no comments yet on this issue.

            Unassigned Unassigned
            psimms_r7 Peter Simms
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: