Put Name Release For Free

We can create partial or sub-templates in helm, mainly known as ?named templates?. A named template is simply a template defined inside a file and given a name. We can consider the named templates just like functions. Named templates will allow us to reuse syntax or logic throughout the helm chart.

To get the values for a Helm release, you can use the helm get values command. This command will retrieve the values that were used to the specified release. Replace <release-name> with the name of the release that you want to retrieve the values for.

ReleaseName is the name you assigned to this installation instance. Chart is the name and location of the chart: oc-cn-helm-chart for BRM cloud native services, oc-cn-ece-helm-chart for ECE cloud native services, or oc-cn-init-db-helm-chart for initializing the BRM database schema.

ReleaseName is the name you assigned to this installation instance. NameSpace is the name space in which the BRM Kubernetes objects reside.

Default and custom deployment values To specify a release's name, use the --name flag : $ helm --name CustomerDB stable/mysql. To deploy the release into a Kubernetes namespace, use the --namespace flag: $ helm --namespace ordering-system stable/mysql.

A named template (sometimes called a partial or a subtemplate) is simply a template defined inside of a file, and given a name. We'll see two ways to create them, and a few different ways to use them.

In the previous section, we use {{ . Release.Name }} to insert the name of a release into a template. Release is one of the top-level objects that you can access in your templates.