Add and Verify the Helm Repository

helm is a tool for packaging and deploying kubernetes applications kron pam secrets management agent components are installed from a helm chart repository that kron technologies publishes in this step, we register that repository with helm helm repository commands command what it does helm repo list lists registered repositories helm repo add \<name> \<url> adds a new chart repository helm repo update refreshes the chart list/versions in the repo (metadata only, not the container image) helm list a lists installed releases across all namespaces in the cluster kron pam secrets management agent charts are published in a single public helm repository register it as follows helm repo list helm repo add kron pam https //krontechnology github io/kron pam aapm helmcharts/ helm repo update helm list a the repository must be registered under the name kron pam all helm install commands in this guide reference charts as kron pam/\<chart name> if you choose a different local repository name, you must change the chart reference in every subsequent command accordingly if the repository is already registered and you want to overwrite it (because the url has changed) helm repo add kron pam https //krontechnology github io/kron pam aapm helmcharts/ force update helm repo update verify that the repository is reachable and that the charts are visible helm repo list helm search repo kron pam expected result helm list a should return empty (on a clean environment) if it isn't empty, don't proceed without cleaning prior to installations—there is a risk of conflict see the section “uninstalling and cleaning up" helm repo update refreshes chart metadata only (the repository index yaml) it doesn't update container images if an image was rebuilt and pushed to the registry under the same tag, no helm operation will pull it, because the default imagepullpolicy is ifnotpresent and the old image is already cached on the node in that case the cached image must be removed from the node and the workload restarted — see the troubleshooting section chart inventory all three components are published under the same kron pam repository charts in the kron pam repository chart release name used in this guide namespace container image(s) pulled kron pam/kron aapm agent kron aapm agent ns agent krontechnology/aapm agent kron pam/aapm service aapm service kron pam aapm krontechnology/aapm service kron pam/kron aapm sidecar kron aapm sidecar ns sidecar krontechnology/aapm sidecar injector (the injector itself) and krontechnology/aapm client (the container injected into target pods) aapm client isn't installed as a separate helm release it is injected into target pods by the kron aapm sidecar chart, and its image is controlled by the sidecarimage values of that chart kron aapm sidecar registers cluster scoped resources (clusterrole, clusterrolebinding, mutatingwebhookconfiguration) therefore only one instance of this chart can run per cluster a second installation will fail or silently conflict on identically named cluster scoped objects inspecting chart versions and default values before installing, list the available chart versions and review the chart defaults chart inspection commands command what it does helm search repo kron pam versions lists every available version of every chart in the repository, together with its app version helm show chart kron pam/\<chart> displays chart metadata, including appversion, which supplies the default image tag helm show values kron pam/\<chart> prints the chart's complete default values yaml — use this to discover every configurable parameter helm show values kron pam/\<chart> > values default yaml saves the defaults to a file so they can be edited and reused helm search repo kron pam versions helm show chart kron pam/kron aapm sidecar helm show values kron pam/kron aapm sidecar to install a specific, pinned chart version rather than the latest one, add version to the install command helm install kron aapm agent kron pam/kron aapm agent version \<chart version> pin the chart version with version in production environments without it, a later helm repo update followed by a reinstall may silently pull a newer chart with different defaults by default, the image tag of each chart is derived from the chart's appversion this is why sidecarimage tag may need to be overridden explicitly, as described in the injector installation and troubleshooting section