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
According to the steps on the official website, after learning the installation part of Helm 3, you will learn about the use of Helm 3. But I think before knowing how to use it, you should first understand the structure of the chart package and how to write a simple chart, so that when you learn how to use Helm 3 later, you will be more impressed. So this article will give a brief description of the chart's directory structure, functions and writing methods.
1. What is a chart
Charts is the package format Helm will use. It is a collection of files describing Kubernetes related resources. A chart can be used to deploy a simple or complex application. For example, databases, message queues, web services, and so on. The chart is formed by creating a specific directory tree and files, and packaging them into a compressed package with a version number for deployment.
Two, Chart file structure
A chart is a collection with a specific directory tree structure and files. The directory name is the name of the chart (no version information). For example, a chart describing WordPress will be stored in the wordpress directory: