Using Helm Dependencies for third party charts
When you are installing packages into a Kubernetes cluster, the go-to solution for software writers is to provide a Helm chart with a default values.yaml file to allow you to easily deploy all of the required resources for their application with a few commands.
You will normally see something like this when you are looking for installation instructions via Helm.
First add our helm charts repo to your helm client
helm repo add..Next, install our chart via helm using
helm install..This increases in complexity depending on the number of charts required to install a full working solution (I’m looking at you istio..) Where you may have 3/4 separate charts to install with different values required.
Additionally, I am not a fan of this approach as I like to deploy all infrastructure and packages via “GitOps” which allows for change control management as well as easy restore in the event of a cluster failure (eg redeploying from a git repo with my values stored in it is easier than finding the helm repo add && helm install commands for the wide range of services I’m now running in my cluster.
