fix existing media pvc issues

Signed-off-by: Bernard Gütermann <[email protected]>

README.md

@@ -177,6 +177,9 @@ transmission:
 
 See the chart [values.yaml](charts/k8s-mediamanager/values.yaml) for more details on available parameters.
 
+If you already have pre-existing volumes you can patch them using the `helm-adopt.sh` script to avoid having the 
+`error : resources already exist` issue when running the install script
+
 ## Usage
 
 Upon deploying the chart with the command above the following endpoints will become available externally:

charts/k8s-mediamanager/templates/sharedStorage.pvc.yaml

@@ -1,4 +1,5 @@
 {{- with .Values.general.sharedStorage }}
+{{- if not (lookup "v1" "persistentVolumeClaim" "" .persistentVolumeClaim.claimName) }}
 apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
@@ -22,4 +23,5 @@ spec:
   selector:
   {{- toYaml . | nindent 4 }}
   {{- end }}
+{{- end }}
 {{- end }}

helm-adopt.sh

@@ -0,0 +1,14 @@
+#!/bin/sh
+
+# This script is used to adopt pre-existing pvcs into a Helm release. It is used in the
+# following way:
+#  helm-adpot.sh <namespace> <release-name>
+
+[ "$#" -eq 2 ] || { echo "Usage: $0 <namespace> <release-name>"; exit 1; }
+
+NAMESPACE=$1
+RELEASE_NAME=$2
+kubectl get -n $NAMESPACE pvc -o name | xargs -I % kubectl label -n $NAMESPACE % app.kubernetes.io/managed-by=Helm
+kubectl get -n $NAMESPACE pvc -o name | xargs -I % kubectl annotate -n $NAMESPACE % meta.helm.sh/release-name=$RELEASE_NAME
+kubectl get -n $NAMESPACE pvc -o name | xargs -I % kubectl annotate -n $NAMESPACE % meta.helm.sh/release-namespace=$NAMESPACE
+kubectl get -n $NAMESPACE pvc -o name | xargs -I % kubectl annotate -n $NAMESPACE % helm.sh/resource-policy=keep