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

Add Volumesnapshot as option for Kubernetes pod workspace volume

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: kubernetes-plugin
    • Labels:
      None
    • Environment:
      Jenkins: 2.277.2
      Kubernetes plugin: 1.29.2
    • Similar Issues:

      Description

      Since Kubernetes release 1.12 the idea of a volumesnapshot has existed, where the state of a persistent volume is captured so that it can be recreated in the future. This feature was released to beta in K8s 1.17 and GA in 1.20. 

      My use case is Yocto, where a majority of the embedded kernel does not change and only a relatively small number of applications are altered frequently. At the moment, using dynamic persistent volume claims, the entire kernel needs to be rebuilt every time, leading to complaints from developers about long build times. If I could capture a volume snapshot with a complete build of our image, then I could make use of Yocto's tools to handle incremental building and the like.

      In Jenkins, an additional option in the pod template Workspace Volume dropdown would be added called Volume Snapshot. When selected, the user would need to enter the name of the existing volume snapshot that would be used to create a dynamic persistent volume for builds using that pod template. Or feel free to choose a better implementation, since you are the experts.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            faroguy0 Ian Panzer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: