search

fluxcd / helm-controller

The GitOps Toolkit Helm reconciler, for declarative Helming
https://fluxcd.io
Apache License 2.0
408 stars 163 forks source link

Ability to watch final values after merging ConfigMaps and Inline values #1093

Open DanielAntos90 opened 1 day ago

DanielAntos90 commented 1 day ago

Currently, when using the Flux Helm Controller, the final applied configuration (after merging ConfigMaps and inline values) is not easily observable. This makes it difficult to troubleshoot or verify the final state of the configuration that is passed to Helm releases.

I would like the Flux Helm Controller to provide a feature that allows us to observe or output the final ConfigMap that is applied to the Helm release. This would include the merged result of all ConfigMaps and inline values defined in the Helm release values.

I propose enhancing the HelmRelease Custom Resource Definition (CRD) to include the final merged ConfigMap in the status section. This would represent the merged result of all ConfigMaps and inline values defined in the Helm release.

This would greatly help with debugging and visibility into the actual configurations being applied by Helm, especially in complex deployments where multiple ConfigMaps and inline values are used.

stefanprodan commented 1 day ago

Values contain secrets, having those in the HR status would result in a CVE, while Kubernetes secrets are encrypted at rest in etcd, custom resources aren’t.

I plan to develop a command in the Flux CLI that will display the final values in stdout.

PadreSVK commented 1 day ago

Values contain secrets, having those in the HR status would result in a CVE, while Kubernetes secrets are encrypted at rest in etcd, custom resources aren’t.

I plan to develop a command in the Flux CLI that will display the final values in stdout.

@stefanprodan is there any possibility to have result values configmap similar to xyz-values config map?