Add extraObjects support to the Weblate Helm chart #726
Description
Describe the problem
The Weblate Helm chart currently does not allow deploying additional Kubernetes resources that share the same lifecycle as the Helm release.
In real deployments, users often need to create extra objects tightly coupled to Weblate (e.g. for resilience or operations). An example i need for my org, is a Velero Schedule to back up Weblate data/PV.
Today, this requires managing separate manifests or custom templates outside the chart, which reduces portability and maintainability.
Solution brainstorm
Add a new Helm value extraObjects allowing users to define arbitrary Kubernetes YAML objects that are deployed with the chart and follow the same lifecycle (install/upgrade/uninstall).
extraObjects:
- apiVersion: velero.io/v1
kind: Schedule
metadata:
name: weblate-backup
spec:
schedule: "0 2 * * *"
template:
includedNamespaces:
- weblate
Implementation could be done via a simple template iterating over .Values.extraObjects and rendering them using toYaml / tpl.
This keeps the chart flexible, avoids forks, and enables use cases like backups, network policies, or other operational resources.
Describe alternatives you have considered
No response
Screenshots
No response
Additional context
No response