Shulou(Shulou.com)06/01 Report--

Today, I would like to talk to you about what the Helm architecture is like, many people may not know much about it. In order to make you understand better, the editor summarized the following content for you. I hope you can get something from this article.

Before putting it into practice, let's take a look at the architecture of Helm.

Helm has two important concepts: chart and release.

Chart is a collection of information to create an application, including configuration templates, parameter definitions, dependencies, documentation, etc., for various Kubernetes objects. Chart is the self-contained logical unit of application deployment. Think of chart as a software installation package in apt and yum.

Release is a running instance of chart and represents a running application. When chart is installed into the Kubernetes cluster, a release is generated. Chart can be installed to the same cluster multiple times, with each installation being a release.

Helm is a package management tool, and the package here refers to chart. Helm can:

Create a new chart from scratch.

Interact with the repository that stores the chart to pull, save, and update the chart.

Install and uninstall release in the Kubernetes cluster.

Update, roll back, and test release.

Helm consists of two components: the Helm client and the Tiller server.

The Helm client is a command-line tool used by end users, and users can:

Develop chart locally.

Manage chart warehouse.

Interact with the Tiller server.

Install chart on a remote Kubernetes cluster.

View release information.

Upgrade or uninstall an existing release.

The Tiller server, which runs in a Kubernetes cluster, processes requests from Helm clients and interacts with Kubernetes API Server. The Tiller server is responsible for:

Listen for requests from Helm clients.

Build release through chart.

Install chart in Kubernetes and track the status of release.

Upgrade or uninstall an existing release via API Server.

To put it simply: the Helm client is responsible for managing the chart;Tiller server is responsible for managing release.

After reading the above, do you have any further understanding of the Helm architecture? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.