Example values.yaml using Release generated environment variables
name_templateto name objects in kubernetes. Helm charts will populate
.Release.namewith the value specified by the
name_template. Release by default sets the
name_templateto the name of the application that's defined in your application configuration.
Example of overriding the default
name_templateset by Release
name_templateis 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_templatewhich may require you to adjust hostnames for internal networking when using the same application template for two applications.
Example of how
name_templateaffects the naming of the deployments
name_templateaffects the services naming and ultimately how your services will reference one another.
env_filedefinition for Helm charts
env_filebased on the
CUSTOMER_NAMEenvironment variable set in Release.
values.yamlto properly start up your containers.
The table above shows example generated values for a container build named
<SERVICE>_REGISTRY_IMAGE_SHAenvironment variables to be used in the Helm
values.yamlfile. 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.
values.yamlfile which references a build generated by Release
Example Helm chart template which references a build generated by Release
values.yamland properly reference the container image built by Release.