# Kubernetes Profiles

Tempest manages your **kubeconfig** files as first-class connection profiles. Each profile gets its own tab with the `KUBECONFIG` environment variable pre-set, so `kubectl`, `helm`, `k9s`, `kustomize`, and any other CLI tool just work — no manual context switching.

This solves the everyday "which cluster am I talking to?" problem: dev cluster in tab 1, staging in tab 2, prod in tab 3 — never type `kubectl config use-context` again.

## Add a kubeconfig

1. Open the **New Kubeconfig** dialog.

   <figure><img src="/files/dCPjGzxYcJFVl9KBSSVA" alt=""><figcaption></figcaption></figure>
2. Paste a kubeconfig YAML or load from a file. Tempest parses the contexts inside.
3. Click **Connect**. Tempest opens your local terminal with `KUBECONFIG` already pointing at this profile.

## Use kubectl, helm, k9s

Inside the tab, run any tool exactly as you would in a normal shell:

```bash
kubectl get pods -A
helm list -A
k9s
```

**Tip**: keep one kubeconfig profile open per cluster — different tabs can target different clusters at the same time without env-var conflicts.

## Install the Kubernetes CLI

Tempest doesn't bundle `kubectl` — install it once with your platform's package manager.

| Platform            | Install command                                                                             |
| ------------------- | ------------------------------------------------------------------------------------------- |
| **macOS**           | `brew install kubectl` (requires [Homebrew](https://brew.sh))                               |
| **Windows**         | `scoop install kubectl` (requires [Scoop](https://scoop.sh))                                |
| **Ubuntu / Debian** | See [official install guide](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/) |

For `helm` and `k9s` use the same package managers (`brew install helm k9s`, `scoop install helm k9s`).

## See also

* [SSH Client for Teleport, Cloudflare Access, AWS SSM, GCP IAP & Tailscale](/connect-to-servers/ssh-client-for-teleport-cloudflare-access-aws-ssm-gcp-iap-and-tailscale.md) — many production Kubernetes clusters live behind these zero-trust gateways
* [Tempest AI Assistant](/productivity/tempest-ai-assistant.md) — ask the AI to draft `kubectl` commands and pipe results back into the terminal


---

# Agent Instructions: 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:

```
GET https://docs.gotempest.app/productivity/kubernetes-profiles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.