Searching for detailed Helm 3 documents on the Internet failed, the official website documents were too messy, and the technical group consulted on the document information and was ridiculed. MD doesn't fight for steamed buns. If there is no good document, I will summarize a document by myself. Part of the content in the document comes from major blogs and official websites, and part of the text content has been rearranged by me. All concept explanations will be accompanied by actual code records and experience. The article is updated from time to time, welcome to follow and subscribe to the column. If you have any questions, please leave a message in the comment area.
Link to the original text of this column: https://blog.csdn.net/xzk9381/category_10895812.html, please indicate the source for reprinting
When writing the first chart in the previous article, we referenced a Helm built-in object .Relases.Name. This built-in object can get the name of the release when the chart is installed and inject it into the template for replacement.
In fact, the built-in objects provided in Helm are very easy to understand. An object can be a simple value, or it can contain other objects or methods. For example, the aforementioned .Relases.Name. Name is an object under the Release object. The Release object is one of the high-level objects that can be accessed in the template. The following describes some of the built-in objects.
Helm's built-in objects all start with capital letters, so it is recommended to follow this naming rule in actual use.
One, the Release object
ReleaseThe object describes the version release itself. It contains the following objects:
| Object name | description |
|---|---|
Release.Name</ |