fix: use multi-source ArgoCD Application for Plex

- Separate chart source (kube-plex) and values source (turingpi)
- Deploy to default namespace where existing PVCs are located
- Use complete plex_values.yml for proper GPU and persistence config
- Fixes storage class and duplicate port issues

applications/plex.yaml

@@ -17,34 +17,21 @@ metadata:
     argocd-image-updater.argoproj.io/git-commit-message: "chore: update Plex image to {{.NewTag}}"
 spec:
   project: default
-  source:
-    # Use our separate kube-plex repository with GPU support changes
-    repoURL: http://gitea-http.gitea.svc.cluster.local:3000/admin/kube-plex.git
+  sources:
+    - repoURL: http://gitea-http.gitea.svc.cluster.local:3000/admin/kube-plex.git
       path: charts/kube-plex
       targetRevision: HEAD
+      ref: charts
       helm:
         releaseName: plex
-      # Override with values from our Gitea repository
-      parameters:
-        - name: image.repository
-          value: linuxserver/plex
-        - name: image.tag
-          value: "1.41.8"
-        - name: claimToken
-          value: "claim-Ku2YYmJzDB1mpyG6YD7x"
-        - name: timezone
-          value: "Europe/Amsterdam"
-        - name: service.type
-          value: "LoadBalancer"
-        - name: service.port
-          value: "32400"
-        - name: rbac.create
-          value: "true"
-        - name: kubePlex.enabled
-          value: "false"
+        valueFiles:
+          - $values/helm-values/plex_values.yml
+    - repoURL: http://gitea-http.gitea.svc.cluster.local:3000/admin/turingpi.git
+      targetRevision: HEAD
+      ref: values
   destination:
     server: https://kubernetes.default.svc
-    namespace: plex
+    namespace: default
   syncPolicy:
     automated:
       prune: true