rename to clone pvc

pvc-copy-tool/Chart.yaml → clone-pvc/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v2
-name: pvc-copy-tool
+name: clone-pvc
 description: A job for copying contents from one PV to another
 type: application
 version: 1.0.0

pvc-copy-tool/README.md → clone-pvc/README.md

@@ -1,8 +1,8 @@
-# Pvc Copy Tool
+# Clone PVC
 
-The pvc copy tool is designed to copy the contents of one PersistentVolume (PV) to a newly created PersistentVolumeClaim (PVC). This tool is especially useful when migrating PersistentVolumes to a new StorageClass or when you need to resize a PV that belongs to a StorageClass that doesn’t support resizing.
+The clone PVC is designed to copy the contents of one PersistentVolume (PV) to a newly created PersistentVolumeClaim (PVC). Clone pvc is especially useful when migrating PersistentVolumes to a new StorageClass or when you need to resize a PV that belongs to a StorageClass that doesn’t support resizing.
 
-The tool employs a workaround for reclaiming PVs, which is necessary to handle ReadWriteOnce (RWO) PVs. If you're working with a ReadWriteMany (RWX) PV, you can directly run a copy job and attach the Job-Pod to the existing PVC—there's no need to create a new PVC.
+The clone PVC employs a workaround for reclaiming PVs, which is necessary to handle ReadWriteOnce (RWO) PVs. If you're working with a ReadWriteMany (RWX) PV, you can directly run a copy job and attach the Job-Pod to the existing PVC—there's no need to create a new PVC.
 
 Use Cases
 
@@ -14,12 +14,12 @@ Use Cases
 
 ### Step-by-Step Process
 
-**1. Clone the Repository:** First, clone the repository that contains the pvc-copy-tool.
+**1. Clone the Repository:** First, clone the repository that contains the clone PVC.
 
 ```bash
 git clone https://github.com/stakater/charts
 
-cd pvc-copy-tool
+cd clone-pvc
 ```
 
 **2. Identify the PV to Copy:** Find the PersistentVolume (PV) you wish to copy.
@@ -59,28 +59,28 @@ Once the data has been copied and the Job has been deleted, you can rebind the P
 
 #### Example Helm Chart Deployment for One-Off Job
 
-To deploy the tool as a one-off job, you can use the following example Helm chart configuration:
+To deploy the clone PVC as a one-off job, you can use the following example Helm chart configuration:
 
 ```yaml
 apiVersion: argoproj.io/v1alpha1
 kind: Application
 metadata:
-  name: pvc-copy-tool
+  name: clone-pvc
   namespace: argocd
 spec:
   destination:
     namespace: <target-namespace>
     server: https://kubernetes.default.svc
   source:
-    path: pvc-copy-tool
-    repoURL: ssh://[email protected]:stakater/pvc-copy-tool.git
+    path: clone-pvc
+    repoURL: ssh://[email protected]:stakater/charts
     targetRevision: master
     helm:
       parameters:
         - name: oldPvName
           value: "<target-pv>"
         - name: newPvcName
-          value: "image-registry-storage-clone"
+          value: "clone-pvc"
         - name: newPvcStorageClass
           value: ""
         - name: newPvcSize

pvc-copy-tool/templates/copy-job.yaml → clone-pvc/templates/copy-job.yaml

@@ -1,7 +1,7 @@
 apiVersion: batch/v1
 kind: Job
 metadata:
-  name: pvc-copy-tool
+  name: clone-pvc
 spec:
   template:
     spec: