This example shows the many ways you can deploy Helm Charts with Zarf. To learn more about how charts
work in Zarf, see the Helm Charts section of the package components documentation.
description : Example showcasing multiple ways to deploy helm charts
# Charts are organized in a list with unique chart names per component - note that a Zarf chart name does not need to match the chart name in a Chart.yaml
namespace : podinfo-from-local-chart
# In this case `localPath` will load the podinfo chart that is located in the `chart` directory
# Variables are used to override the default values in the chart
# This can be overridden by the user at deployment time with the `--set` flag
description : " Override the number of pod replicas "
namespace : podinfo-from-oci
# In this case `url` will load the helm chart located in the podinfo OCI repository
url : oci://ghcr.io/stefanprodan/charts/podinfo
namespace : podinfo-from-git
# In this case `url` will load the helm chart located in the podinfo git repository
url : https://github.com/stefanprodan/podinfo.git
# By default git will look in the root of the git repository but you can define a sub directory with `gitPath`
namespace : podinfo-from-repo
# In this case `url` will load the helm chart located in the podinfo helm repository
url : https://stefanprodan.github.io/podinfo
# By default the chart `name` will be what is used to search a repository but since Zarf chart names must be unique per-component you can override this with `repoName`
# By default the release name will be the chart name, but you can override this with the `releaseName` key
releaseName : cool-release-name
- ghcr.io/stefanprodan/podinfo:6.4.0
# This is the cosign signature for the podinfo image for image signature verification
- ghcr.io/stefanprodan/podinfo:sha256-57a654ace69ec02ba8973093b6a786faa15640575fbf0dbb603db55aca2ccec8.sig