Use an existing PVC as config volume

[koiralasandesh]

Use an existing PVC as a config volume

• Added config.persistence. existingClaim

• Specify an existing PVC managed by user

• Default PVC in the chart is not created if this value exists

• Fixes feat(helm): add an option to specify no PVC or a preexisting one #1433

How Has This Been Tested?

Tested in a rke2 k8s cluster

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• New Features

  • Support specifying an existing PersistentVolumeClaim to reuse storage; when provided, the default PVC will not be created.

• Documentation

  • Updated chart README and values table to document the new existingClaim option and reflect the new chart version.

• Chores

  • Chart version bumped to 3.1.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Chart version bumped and a new config.persistence.existingClaim value added. Templates now conditionally skip creating a PersistentVolumeClaim and the StatefulSet uses the existing claim name when provided.

Changes

Cohort / File(s)	Summary
Chart metadata & README charts/seerr-chart/Chart.yaml, charts/seerr-chart/README.md	Chart version bumped from 3.0.2 to 3.1.0. README badges updated and documentation added for the new config.persistence.existingClaim value.
Values charts/seerr-chart/values.yaml	Added config.persistence.existingClaim (string) to allow specifying an existing PersistentVolumeClaim; documented that the default PVC will not be created when provided.
Templates: PVC rendering charts/seerr-chart/templates/persistentvolumeclaim.yaml	PVC template wrapped in a conditional so the PVC is rendered only when .Values.config.persistence.existingClaim is not set.
Templates: StatefulSet claim reference charts/seerr-chart/templates/statefulset.yaml	Volume claimName for the config volume now uses .Values.config.persistence.existingClaim if provided, otherwise falls back to the generated persistence name.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• fallenbagel
• sudo-kraken
• 0xSysR3ll

Poem

🐰 I nibbled charts beneath the moonlight glow,
I added a name that migrations now know.
PVCs skip their birth with a gentle claim,
Old volumes welcomed — the config's the same.
Hop, patch, and deploy — a rabbit's tiny aim.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR partially implements issue #1433 by adding support for using an existing PVC, but does not implement the emptyDir option for no PVC creation.	Implement the emptyDir option for cases where no PVC should be created, as requested in issue #1433.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: allowing users to specify an existing PVC for the config volume instead of creating a new one.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly scoped to implementing the existing PVC feature: configuration values, documentation, and template conditionals.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into develop

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[M0NsTeRRR]

@koiralasandesh thanks for your contribution :)