Docs / Clouds
Linode (Akamai)
Connect a Linode / Akamai Cloud account with a personal access token to manage instances and LKE clusters.
Pangea authenticates to Linode (Akamai Cloud) with a personal access token. The agent can then work with your Linodes and managed Kubernetes (LKE) clusters.
Connect
Create a personal access token
In the Linode Cloud Manager, go to Profile → API Tokens and create a personal access token. Give it read access for inspection, or read/write access when changes are needed, to:
- Linodes
- Kubernetes (LKE)
The token is shown once. Copy it.
Connect in Pangea
In Connectors → Connect → Linode, enter:
| Field | Notes |
|---|---|
| Label | A friendly name, for example "My Linode Account" |
| Personal Access Token | The token you created |
Pangea checks the token before it saves. An invalid or revoked token is rejected. The token is stored encrypted.
In the Pangea app
- Kubernetes clusters: your LKE clusters appear next to EKS and GKE. Pangea pulls the kubeconfig for you, so you can browse workloads, open pod terminals and stream logs with no manual setup.
- Compute and access: your Linode instances appear with status and details next to the rest of your fleet.
What the agent can do for you
The agent can list your Linodes and LKE clusters and operate the clusters with the same Kubernetes tooling it uses everywhere else. Ask it things like:
- "Why is the
workerdeployment on LKE stuck pending?" It reads events, node status and config to find the cause. - "Which of my Linodes is running out of disk?" It inspects the fleet and reports back.
The agent can also reach other Linode API resources within the token's scopes, even though the app only lists instances and clusters.
Permissions and authorization
Team Administrators connect and remove this binding and can restrict it with a member allow-list. Select the connection for the conversation before you ask the agent to use it. The token's scopes stay the outer limit, whatever the prompt or permission mode.
Individual actions follow Auto Mode and Full Access. Significant cloud infrastructure work uses plans. A routine API action does not create a plan on its own, so say so explicitly when you want to review changes first.
Good to know
- A personal access token is a long-lived credential. It lasts until its expiry date or until you revoke it. Pangea does not shorten it.
- Linode tokens can carry an expiry date. That is a good safety net; just rotate the binding before it lapses.
- To keep environments apart, create one token per purpose and connect each as its own binding, with its own allow-list.