@@ -7,12 +7,13 @@ Objects can be simple, and have just one value. Or they can contain other object
In the previous section, we use `{{.Release.Name}}` to insert the name of a release into a template. `Release` is one of four top-level objects that you can access in your templates.
-`Release`: This object describes the release itself. It has several objects inside of it:
-`Release.Name`: The release name
-`Release.Time`: The time of the release
-`Release.Namespace`: The namespace to be released into (if the manifest doesn't override)
-`Release.Service`: The name of the releasing service (always `Tiller`).
-`Release.Name`: The release name
-`Release.Time`: The time of the release
-`Release.Namespace`: The namespace to be released into (if the manifest doesn't override)
-`Release.Service`: The name of the releasing service (always `Tiller`).
-`Release.Revision`: The revision number of this release. It begins at 1 and is incremented for each `helm upgrade`.
-`Release.IsUpgrade`: This is set to `true` if the current operation is an upgrade.
-`Release.IsUpgrade`: This is set to `true` if the current operation is an upgrade or rollback.
-`Release.IsInstall`: This is set to `true` if the current operation is an install.
-`Values`: Values passed into the template from the `values.yaml` file and from user-supplied files. By default, `Values` is empty.
-`Chart`: The contents of the `Chart.yaml` file. Any data in `Chart.yaml` will be accessible here. For example `{{.Chart.Name}}-{{.Chart.Version}}` will print out the `mychart-0.1.0`.
- The available fields are listed in the [Charts Guide](charts.md)