Feature Request: Add support for extraDeploy in Helm chart #57
Description
Issue submitter TODO list
- I've looked up my issue in FAQ
- I've searched for an already existing issues here (legacy) and here
- I've tried installing latest charts and the issue still persists there
- I'm running a supported version of the application & chart which is listed here
Describe the bug (actual behavior)
Summary
Please add support for an extraDeploy feature to allow injecting custom Kubernetes manifests directly through the chart via values.yaml.
⸻
Use Case
Sometimes, users need to deploy additional Kubernetes objects (like ConfigMaps, Secrets, ServiceMonitors, or custom CRDs) alongside the main chart — without maintaining a fork or custom overlay.
Having an extraDeploy section (similar to Bitnami charts) would make it easy to include small custom manifests directly in values.yaml, enabling more flexibility for environment-specific setups.
In this chart, i want to create a UI secret which is passed in values file as -
yamlApplicationConfigSecret:
name: kafka-ui-config-secret
keyName: config.yml
Now I am creating kafka-ui-config-secret secret using external secret operator, so need to create this template via extraDeploy feature.
Expected behavior
No response
Your installation details
Chart version - 1.5.1
Steps to reproduce
NA
Screenshots
No response
Logs
No response
Additional context
Some helpful resources:
util to render the deploys:
https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_tplvalues.tpl
Usage:
{{- range .Values.extraDeploy }}
---
{{ include "common.tplvalues.render" (dict "value" . "context" $) }}
{{- end }}
Example - https://github.com/bitnami/charts/blob/main/bitnami/kube-prometheus/templates/extra-list.yaml