0
votes

I may just be extremely slow, but I cannot wrap my head around this.

  • There are repositories/hubs (artifacthub, etc.) with pointers to other repos that have helm charts
  • I can add these charts as a 'dependency' in my helm Chart.yaml file, if I know the name/version/repository
  • For example, for https://artifacthub.io/packages/helm/vultr/cert-manager-webhook-vultr the version=1.0.0, the dependency=vultr/cert-manager-webhook-vultr, and the repo=https://vultr.github.io/helm-charts (is this correct? Why are these 3 values not super visible. It always seems like a guessing game when trying to pull down charts)
  • On artifacthub, there is a 'templates' section, which has various yaml files. Is this what properties are possible to modify on the chart? How do these helm template yamls that I define get applied to charts I have installed? (For example, if I have both nginx and traefik ingresses, will both of them get all the yamls for kind:Ingress applied to them?)
  • Why does helm require me to pull down the cluster to my local repo to use it? Do people use helm to track releases in 'the real world'?
  • In what scenario would I just do 'helm install X' as opposed to adding it to my Chart.yaml dependencies?

The helm docs (and lots of tutorials) are very terse and only show one off script examples. Shouldn't I want all of my 'infrastructure as code'? I don't understand the constant suggestions to 'helm add repo' and 'helm install' and then hand wave over any customization?