Connecting to a Cluster Using the Local Helm Client

Last updated: 2020-09-03 14:58:48

    Operation Scenario

    This document explains how to connect to a cluster by using local Helm client.

    Directions

    Downloading the Helm client

    Run the following commands in sequence to download the Helm client. For more information on installing Helm, see Installing Helm.

     curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3
    chmod 700 get_helm.sh
    ./get_helm.sh

    Configuring a Helm Chart repository (optional)

    1. Run the following command to configure the official Kubernetes repository.
      helm repo add stable https://kubernetes-charts.storage.googleapis.com/
    2. Run the following command to configure the Tencent Cloud application market.
      helm repo add tkemarket https://market-tke.tencentcloudcr.com/chartrepo/opensource-stable
    3. Configure a TCR private Helm repository.

    Connecting to a cluster

    Compared with Helm v2, Helm v3 has removed the Tiller component. The Helm client can directly connect to the API servers of clusters. The application-related version data is stored in Kubernetes. See the figure below:

    The Helm client uses a client certificate generated by TKE to access clusters. The detailed directions are as follows:

    1. Use the TKE console or APIs to obtain an available Kubeconfig for public or private network access.
    2. Connect to the target cluster by referring to the following two methods:
      • Use the kubeconfig obtained above to configure kubectl config use-contest on the device where the Helm client is located.
      • Run the following command with the specified parameter to access the target cluster.
        helm  install ....  --kubeconfig [path of kubeconfig]

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help