Skip to main content
At the end of this guide a cluster you already run (EKS, GKE, AKS, k3s, kind, minikube or on-premises) is connected to Ankra through the Ankra agent. Connecting takes about a minute once the things below are in place. Ankra then reads the cluster and deploys nothing until you ask.

Before you start

  • A payment method on the organisation. Ankra asks for a card before a first cluster of your own. Saving it charges nothing, and the first 30 worker vCPUs are free. Without one, Ankra refuses to add the cluster: Ankra connects a cluster only for an organisation with a payment method on file. Free credit does not replace it: without one, adding the cluster is refused. The guide below lets you save the card on the way. See Billing.
  • helm and kubectl on a computer that reaches the cluster. The account your kubectl uses must be allowed to create a namespace and cluster-wide roles.
  • Outbound network access from the cluster to platform.ankra.app on port 443 (the Ankra API), command.platform.ankra.app on port 4222 (the channel Ankra sends work over, TLS) and registry.ankra.cloud on port 443 (the agent image and its chart). Nothing inbound is needed.
  • A default StorageClass, if you will deploy anything that keeps data. Without one, a volume that an add-on asks for stays Pending. Check before you start: the class marked (default) is the one new volumes get.

Connect the cluster

1

Choose Connect my own cluster

On Where do you want to start? (/next/onboarding), under Connect my own cluster, press Connect my cluster. On a phone the choice says Needs your computer: email yourself the step, because the command runs in a terminal.Check: the heading reads Connect your cluster. Next to Name in Ankra: is a suggested name. Press the pen beside it to change it.
2

Say what the cluster runs

Under What does this cluster run?, choose one:
  • Production: Ankra AI never changes it without asking. People and their agents still can.
  • Development or testing: you may later let Ankra AI restart or scale things unasked. That stays off until you turn it on.
Check: the page shows the install command, or asks for a card first.
3

Save a card, if the page asks

When your organisation has no payment method yet, the page says Ankra asks for a card before a first cluster of your own. and shows the command without its token and version, so you can read it first. Press Save a card, add the card, and come back.Check: the command now carries your install token. The page said Your install token appears once it is saved.
4

Run the install command

Optional: type your cluster’s context under kubectl context. It pins every command on the page to that one cluster, so none can run against another.Copy the command exactly as the page shows it and run it in your terminal. It installs the Ankra agent with Helm and carries your cluster’s token and the agent version. Its shape is:
The command carries your cluster’s token, a credential that does not expire. Running it leaves the token in your shell history and in Helm’s release values, where helm get values shows it. Replacing it with ankra cluster agent token --generate, or removing the cluster from Ankra, ends the old one.
Check: the page says Waiting for your cluster’s name to connect. It usually connects within a minute. Check now looks again at once.
5

Check it is online

Check: the heading changes to your cluster’s name is connected, with Ankra installed its own agent and changed nothing else. Press Show me next to See what runs on your cluster and what needs attention.Under What to do next, Open my cluster opens its page in Ankra, where its connection reads Connected.

What Ankra can now see and do

The What it installs, and how to remove it fold on the page says the same, in full. To see everything the chart would create before you install it, without applying anything:
An AI agent you connected with Read and change acts as you, so it reaches this cluster too. Marking the cluster Production does not stop it. The connected page says so and offers Manage its access. See Connect your AI agent.

Put a first add-on on it

Quickstart, step 2 deploys Grafana as a Stack. It works the same on your cluster. If the chart asks for a volume, it uses the default StorageClass from Before you start.

Verify

In Ankra, the cluster’s page shows its connection as Connected. From the CLI, select the cluster and list its storage classes through the agent:
The list matches what kubectl get storageclass shows on the cluster.

Remove it again

Removing a cluster has two halves: in Ankra, and on the cluster.
1

Remove it from Ankra

On the connected page, open Not the one you meant? Remove it and press Remove it from Ankra. This opens the cluster’s Settings → Terminate or remove.Removing it from Ankra ends the Ankra agent’s access at once and deletes nothing on the cluster. The agent stays installed until you take it out.
2

Take the agent out of the cluster

Check: nothing cluster-wide is left. This answers NotFound for both once it is gone:

What can go wrong

When nothing arrives for a while, the page says Nothing from your cluster’s name yet and keeps watching. Open See why: three commands, and what usually stops it for these commands:
Ankra agent covers the agent in more depth.

Other ways to connect

Outside the first screen, open Infrastructure → Clusters and press Connect a cluster. Connect an existing cluster has two tabs: Install the agent (name the cluster, then Get the install command) and Find a managed cluster. Add a cluster covers both, and clusters Ankra builds for you.

Where to go next

Deploy your first Stack

Grafana on your cluster, then a question to Ankra AI about it.

Put your app online

From a GitHub repository to a live address.

Keep it in Git

Connect a repository so every change is reviewed and versioned.

What Ankra can access

The agent, the data Ankra keeps, and how to restrict it.