actions / actions/actions-runner-controller

PVC From Snapshot

Open
#3,966 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community enhancement needs triage
Dominant language
Go
Stars
6.5k
Forks
1.5k
Avg merge
2d 2h
Merged PRs (30d)
27

Description

What would you like added?

I'd love to be able to create a PVC on demand from a snapshot for each runner that I build. We have a significant amount of data we cache in PVCs (100s of GB) and I'd love to be able to create PVC for each runner based on a snapshot with this data.

PVC can be created like so

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-from-snapshot
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 100Gi
    dataSource:
      name: dagger-2025-02-20
      kind: VolumeSnapshot
      apiGroup: snapshot.storage.k8s.io

so I'd hope for some CRD interface like
Note: Feature requests to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Runner image aims to be vendor agnostic.

      volumes:
      - ephemeral:
          volumeClaimTemplate:
            spec:
              accessModes:
              - ReadWriteOnce
              resources:
                requests:
                  storage: 100Gi
                dataSource:
                  name: dagger-2025-02-20
                  kind: VolumeSnapshot
                  apiGroup: snapshot.storage.k8s.io
Why is this needed?

Moving 100s of GB on every build is cumbersome and takes lots of time. just restoring from a snapshot would be great.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides Kubernetes PVC and ephemeral volumeClaimTemplate examples but names no repository files, tests, or entry points. Begin by locating the runner CRD interface and determine how snapshot-backed ephemeral PVCs should be represented; done means the requested interface supports creating a PVC from a snapshot for each runner.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, go, kubernetes
Domain
ci-cd, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.