Cloud Providers

The Cloud Providers extension pulls cluster kubeconfigs from managed-Kubernetes services (EKS, GKE, AKS, and more), so you can connect to them from Kunobi without hunting for credentials by hand.

Kunobi never asks for your cloud API keys. Everything runs through each provider's official CLI: Kunobi installs the CLI for you if needed, opens the provider's own login flow in the integrated terminal, and uses the CLI to list clusters and fetch kubeconfigs. Your credentials live wherever the provider's CLI normally keeps them.

Open the Providers List

1. Click Sources in the left navigation bar.
2. Open the workspace selector in the sidebar (press W) and pick Cloud Providers.

You'll see a table of providers with columns Provider, CLI, Source, and Status. If the extension isn't installed yet, this page shows a "Cloud Providers extension required" notice instead - click Open Extensions and install it (see Extensions).

Step 1 - Install the Provider's CLI

Each provider is driven by its official CLI (aws, gcloud, az, doctl, ...). If you already have it on your PATH, Kunobi detects it and the Status column skips ahead. Otherwise:

1. Select the provider's row.
2. Press Install CLI (or press i).

Kunobi installs the CLI through its built-in tool manager - no separate download needed. The status shows Installing... and then moves on.

Step 2 - Authenticate

1. With the provider row selected, press Authenticate (or press a).
2. Kunobi opens the integrated terminal and runs the provider's own login command - for example aws configure sso for AWS, gcloud auth login for Google Cloud, az login for Azure, or doctl auth init for DigitalOcean. Follow the provider's prompts (usually a browser sign-in).
3. When the login finishes and the terminal session ends, Kunobi re-checks the connection. The Status column turns to Ready, with a tooltip showing which identity you're signed in as.

If your credentials later expire, the status shows Auth failed or Not authenticated - select the row and press Re-authenticate.

Step 3 - Pick a Cluster and Download its Kubeconfig

1. Press Enter (or double-click) on a provider with status Ready to browse it.

2. Step through the provider's hierarchy - each step is a simple table, with a breadcrumb tracking where you are:

   • AWS: Region → Cluster
   • Google Cloud: Project → Location → Cluster
   • Azure: Subscription → Resource Group → Cluster
   • Most other providers go straight to a Cluster list.
   

3. On the cluster you want, press Download (Enter).

Kunobi uses the provider CLI to write a dedicated kubeconfig file for that cluster into your kubeconfig directory (your configured directory, or ~/.kube by default). A "Kubeconfig downloaded" toast confirms it, and because Kunobi watches your kubeconfig directories, the new cluster appears on the Clusters page automatically - connect to it like any other context.

Supported Providers

Provider	Tier
Amazon Web Services (EKS)	Free
Google Cloud (GKE)	Free
Microsoft Azure (AKS)	Pro
DigitalOcean (DOKS)	Pro
Exoscale (SKS)	Pro
Nine (NKE)	Pro
OVHcloud (MKS)	Pro
Scaleway (Kapsule)	Pro
Civo, IBM Cloud (IKS), Linode/Akamai (LKE), Oracle Cloud (OKE), UpCloud (UKS), Vultr (VKE)	Coming soon

Pro providers show a Pro chip in the table - see Plans & Pro. Providers marked Soon are visible but not yet selectable.