Possible Feature request: Support Helm Controller in the Install section

I have a possible feature proposal. I am not sure whether it makes sense or not and please help me to get clarified if i understood the scope of the project wrong. Thanks in Advance 😃

There are several Helm operators available and Helm controller from weave flux looks promising.

Generation of HelmRepository, HelmChart & HelmRelease CRDs greatly helps for those who wanted to install helm charts and reconcile continuously through helm controller.

for suppose to install prometheus helm chart applying below yaml would result in installation & Reconciliation.

apiVersion: helm.fluxcd.io/v1
kind: HelmRelease
metadata:
  name: prometheus
  namespace: default
spec:
  releaseName: prometheus
  targetNamespace: monitoring
  timeout: 300
  resetValues: false
  wait: false
  forceUpgrade: false
  chart:
    repository: https://prometheus-community.github.io/helm-charts
    name: prometheus
    version: 12.0.0
  values:
    replicas: 1

I believe it would be beneficial to have an option in install section to download even helmrelease crd yamls in case anyone wants.

If this feature makes sense, i can pick up this work and contribute if needed.

[vijaySamanuri]

This would also be nice to bring up at the next Flux meeting

Sure @scottrigby. Will attend thursday’s meeting. Thank you 😃

I’d think other ideas should probably be proposed as separate issues

yeah i will 👍

[vijaySamanuri]

I think any auto-generated Flux helm-controller CRD example CR should be made clear it’s an example only

Yeah the helm-controller CRDs would be examples only, and also as you rightly mentioned even the helm commands currently displayed are examples only.

this simple auto generation helps users to get started quickly, this acts like a base, the only thing they have to do is to create an overlay/overrides to customize according to their requirements.

One benefit these helm-controller CRDs provide is “to declaratively manage helm releases and auto reconciliation” which mainly serves production use-cases, unlike the current example helm install commands which are mainly for try out purpose, just fire and forget (loose track i.e no VCS track).