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

Ephemeral volumes for workspace

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • kubernetes-plugin
    • None
    • kubernetes 4174.v4230d0ccd951

      Kubernetes supports https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/ starting around 1.23 to 1.25 depends on the type. One would want to use an ephemeral volume for a workspace volume since it may be faster or otherwise more preferable than what is used by `emptyDir: {}`.

      Currently, there doesn't seem to be a way to override workspace volume definition directly from `podTemplate` yaml - plugin always overrides what I give it and reverts it back to `emptyDir: {}`. Not sure why would that be required.

      Plugin seems to be forcing me to use `workspaceVolume` option on the `podTemplate` which kind of works, but is not ideal. For example, if I wanted to use ephemeral volume with `volumeClaimTemplate`, alternative to that would be to use `dynamicPVC()` to `workspaceVolume` in `podTemplate`. Unfortunately, in this case, Jenkins will take on creating and destroying that PVC and among potential points of failures - it simply takes longer. For some reason I am seeing pod schedule being delayed to 2-3 minutes in some cases for no reason.

      I think a user should get access to override workspace volume directly on the pod template, but if not - a new option for `workspaceVolume` needs to be added to allow for `ephemeral` definition.

            vlatombe Vincent Latombe
            llibicpep Dee Kryvenko
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: