Example values.yaml using Release generated environment variables
name
or name_template
to name objects in kubernetes. Helm charts will populate .Release.name
with the value specified by the name_template
. Release by default sets the name_template
to the name of the application that's defined in your application configuration.Example of overriding the defaultname_template
set by Release
name_template
is useful when creating an application template used for multiple applications or for on-premise deployments. Helm charts often prefix all of the deployments with the name_template
which may require you to adjust hostnames for internal networking when using the same application template for two applications.Example of howname_template
affects the naming of the deployments
name_template
affects the services naming and ultimately how your services will reference one another.Exampleenv_file
definition for Helm charts
env_file
based on the CUSTOMER_NAME
environment variable set in Release.values.yaml
to properly start up your containers.The table above shows example generated values for a container build namedbackend
<SERVICE>_REGISTRY_IMAGE_URL
and <SERVICE>_REGISTRY_IMAGE_SHA
environment variables to be used in the Helm values.yaml
file. Here is a common pattern seen in open source Helm charts when referencing container images. Notice that we set name to [email protected]
to use the container registry SHA.Examplevalues.yaml
file which references a build generated by Release
Example Helm chart template which references a build generated by Release
values.yaml
and properly reference the container image built by Release.