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

1. Introduction of helm

Deploying container cloud applications in Kubernetes is also a challenging task. Helm is a client tool to simplify the installation and deployment of container cloud applications in Kubernetes. Helm can help developers define, install and upgrade container cloud applications in Kubernetes. At the same time, container cloud applications can be shared through helm. Common applications, including Redis, MySQL, and Jenkins, are provided in Kubeapps Hub, which can be deployed and installed in your own Kubernetes cluster with a single command through helm.

1. Helm architecture

The overall architecture of helm is shown in the following figure. The Helm architecture consists of a Helm client, a Tiller server, and a Chart repository; Tiller is deployed in Kubernetes, and the Helm client obtains the Chart installation package from the Chart repository and installs it into the Kubernetes cluster.

Helm is a tool for managing Kubernetes packages, and Helm provides the following capabilities:

Create a new charts; to package charts into tgz files; interact with chart repositories; install and uninstall Kubernetes applications; manage the life cycle of charts installed using Helm; 2. Important concepts of helm

In Helm, there are three important concepts to understand:

Charts: a collection of information to create an Kubernetes application instance, that is, a helm package, which contains all the images, dependencies, resource definitions, etc. needed to run a K8s application, as well as Service resource definitions, which are similar to yum's rpm files; Repository:Chart repositories are used to centrally store and distribute Charts. Config: the configuration information used by the application to instantiate the installation; the running instance of Release:chart, which contains a specific config

In the same cluster, a Charts can be installed repeatedly using different config, with each installation creating a new Release.

3. Helm components

There are two main components in Helm, the Helm client and the Tiller server:

Helm client: is a command line tool for end users.

The client is responsible for the following tasks:

Local chart development; the management repository interacts with the Tiller server (sending the charts that needs to be installed, requesting information about the release, requesting updates, or uninstalling the installed release)

Tiller server: the Tiller service is deployed in the Kubernetes cluster, and the Helm client interacts with the Tiller server and eventually with the Kubernetes API server.

The Tiller server is responsible for the following tasks:

Listen for requests from the Helm client to combine chart and configuration to build a release installed in Kubernetes, and track subsequent releases through interaction with Kubernetes, update or chartII, deploy helm1, install helm client # download helm [root@master ~] # wget https://get.helm.sh/helm-v2.14.3-linux-amd64.tar.gz # unpack from github All you need is a command in the package [root@master ~] # tar zxf helm-v2.14.3-linux-amd64.tar.gz [root@master ~] # mv linux-amd64/helm / usr/local/bin/ [root@master ~] # chmod + x / usr/local/bin/helm # to automatically complete [root@master ~] # echo 'source

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.