> For the complete documentation index, see [llms.txt](https://ibm-developer.gitbook.io/cloudpakforapplications-appmod/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ibm-developer.gitbook.io/cloudpakforapplications-appmod/technology-foundations/helm101/helm-setup.md).

# Setup Helm

For the Helm labs of this workshop we will be using Helm Version 3. If you are running the labs using the IBM Cloud Shell, we need to complete a couple of setup steps before we proceed. This section is broken up into the following steps:

1. [Access the Cloud Shell](/cloudpakforapplications-appmod/technology-foundations/helm101/helm-setup.md#1-access-the-cloud-shell)
2. [Install Helm Version 3](/cloudpakforapplications-appmod/technology-foundations/helm101/helm-setup.md#2-install-helm-version-3)
3. [Configure Kubectl](/cloudpakforapplications-appmod/technology-foundations/helm101/helm-setup.md#3-configure-kubectl)

## 1. Access the Cloud Shell

If you do not already have it open from the workshop setup section, go ahead and open the Cloud shell.

1. From the [IBM Cloud Home Page](https://cloud.ibm.com), select the terminal icon in the upper lefthand menu.

![Terminal Button](/files/-MAmMiOb-pPCboG_lp55)

> *Note: Ensure the cloud shell is using the same account where your cluster is provisioned. Ensure that the account name shown in the top right of the screen, next to `Current account` is the correct one.*

## 2. Install Helm Version 3

The version of Helm that comes pre-configured in the Cloud Shell needs to be updated:

1. Run the following commands to install Helm Version 3

```bash
wget https://get.helm.sh/helm-v3.2.0-linux-amd64.tar.gz
```

```bash
tar -zxvf helm-v3.2.0-linux-amd64.tar.gz
```

```bash
ls -al
```

```bash
echo 'export PATH=$HOME/linux-amd64:$PATH' > .bash_profile
```

```bash
source .bash_profile
```

```bash
helm version --short
```

The result is that you should have Helm Version 3 installed.

```bash
$ helm version --short
v3.2.0+ge11b7ce
```

## 3. Configure Kubectl

If you have not setup your kubectl to access your cluster, you can do so in the Cloud Shell.

1. Run the `ibmcloud ks clusters` command to verify the terminal and setup for access to the cluster

   ```
   ibmcloud ks clusters
   ```
2. Configure the `kubectl` cli available within the terminal for access to your cluster. If you previously stored your cluster name to an environment variable, use that (ie. `$CLUSTER_NAME`), otherwise copy and paste your cluster name from the previous commands output to the `$CLUSTER_NAME` portion below.

   ```
   ibmcloud ks cluster config --cluster $CLUSTER_NAME
   ```
3. Verify access to the Kubernetes API by getting the namespaces.

   ```
   kubectl get namespace
   ```
4. You should see output similar to the following, if so, then your're ready to continue.

```
NAME              STATUS   AGE
default           Active   125m
ibm-cert-store    Active   121m
ibm-system        Active   124m
kube-node-lease   Active   125m
kube-public       Active   125m
kube-system       Active   125m
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ibm-developer.gitbook.io/cloudpakforapplications-appmod/technology-foundations/helm101/helm-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.