Elizabeth W
16 lines
907 B
Markdown
16 lines
907 B
Markdown
# Implementation Plan: Shared PVC Workspace & Git Clone
|
|
|
|
## Objective
|
|
Implement a shared Persistent Volume Claim (PVC) strategy to ensure the repository is only cloned once and all parallel scanners can access the same codebase without re-downloading it.
|
|
|
|
## Requirements
|
|
- Use Argo Workflows `volumeClaimTemplates` to define a temporary PVC for the workflow duration.
|
|
- Create a `clone-repo` task in the DAG.
|
|
- The `clone-repo` task should use a standard git image (e.g., Alpine/Git) to clone the `repo-url` at `git-revision` into the shared PVC mounted at `/workspace`.
|
|
- Ensure all subsequent tasks will mount this PVC at `/workspace`.
|
|
|
|
## Agent Instructions
|
|
1. Modify the `ClusterWorkflowTemplate` to add the `volumeClaimTemplates`.
|
|
2. Add the `clone-repo` task template that executes `git clone`.
|
|
3. Configure the DAG so the parallel scanning steps depend on the successful completion of `clone-repo`.
|