Basic question which I don't seem to find a concrete answer to. How should I keep track of external public charts?

Let's say I want to make use of the :

Kubernetes SIGs AWS Load balancer controller: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/deploy/installation/

I could "imperatively" do the following:

Add the Helm repo:

helm repo add eks https://aws.github.io/eks-charts

Get the image input values

helm show values eks/aws-load-balancer-controller > values.yml

Update the clusterName and install

Install the helm chart if not using IAM roles for service accounts:

helm install aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system  -f values.yml --dry-run

And it will work. But assuming that I have the following directory structure for my Kubernetes IaC:

  ▾ kubernetes/        
    ▸ apps/
    ▾ base/            
      ▾ alb_controller/
          README.md    
          values.yml   
      ▸ daemonsets/    

I'll end up only with a values.yml and the README.md explaining what I did and which external chart I used.

What would be the best way to handle that type of dependencies?

CodePudding user response：

I'm not 100% sure what you're trying to do, but it sounds like you're trying to utilise another external chart as part of your chart, in which case, Chart Dependencies will probably be what you're looking for.

Using Chart Dependencies you can tell Helm you want to install additional charts as part of your chart and Helm will automatically do that whenever you install or upgrade your chart.