Add Helm use case intro page

[scottrigby]

What is the simplest way to explain how Flux works with Helm to existing Helm users?

There's a lot more we can say, but is there anything critical we think should go into an intro that I'm missing?

See fluxcd/website#120

[stefanprodan]

@scottrigby I think we could add a section on secrets management and explain how valuesFrom work with secrets decrypted by kustomize-controller. Another thing that's missing from here is the automated upgrade feature (semver range) and automated rollback.

[scottrigby]

@scottrigby I think we could add a section on secrets management and explain how valuesFrom work with secrets decrypted by kustomize-controller

Should I just summarize and link to the existing doc pages on that?

• https://toolkit.fluxcd.io/components/helm/helmreleases/#values-overrides
• https://toolkit.fluxcd.io/guides/mozilla-sops/
• also configMap doc: https://toolkit.fluxcd.io/guides/helmreleases/#refer-to-values-in-configmaps-generated-with-kustomize
• and a note on how these refs changed from Flux 1 -> 2: https://toolkit.fluxcd.io/guides/helm-operator-migration/#configmap-and-secret-references

[stefanprodan]

Should I just summarize and link to the existing doc pages on that?

Yes, for each topic we need to explain what's the GitOps way of doing it and why it's useful, then link to each doc.

a note on how these refs changed from Flux 1 -> 2

This doc is about v2, I would not mention v1 at all.

[scottrigby]

Another thing that's missing from here is the automated upgrade feature (semver range) and automated rollback.

While there's a note about the feature here https://toolkit.fluxcd.io/components/helm/controller/, and the API pages have details, the best description for this is currently in the Helm Operator -> Controller migration doc https://toolkit.fluxcd.io/guides/helm-operator-migration/#defining-a-rollback-uninstall-configuration and https://toolkit.fluxcd.io/guides/helm-operator-migration/#automated-rollbacks.

Perhaps the bulk of this should be moved to the helm use case intro page, and that section could be linked to from the operator->controller migration page instead of the info living there.

[stefanprodan]

Perhaps the bulk of this should be moved to the helm use case intro page, and that section could be linked to from the operator->controller migration page instead of the info living there.

Let’s copy and adapt the rollback info in this doc. I want to avoid sending people from the migration guide to other places. The audience for this document is very different to the migration one, so duplicating some info is fine.

[scottrigby]

@stefanprodan WDYT? Trying to cover bases with simple examples, while duplicating as little as possible from other areas of the docs. I did follow your suggestion about copying adapt and rollback.

[stefanprodan]

LGTM

Thanks @scottrigby 🏅

[hiddeco]

This is awesome, thank you very much @scottrigby 💯 🥇