helm command. If you need a new one, Ankra can build it on your own cloud account, or create a cluster your cloud provider runs for you. A cluster you import, or one built on your own account, stays yours along with its servers: they keep running if you ever disconnect from Ankra. A Playground and Ankra Cloud (Closed Beta) are the exceptions, because they run on servers Ankra operates.
Which path is mine?
Connect an existing cluster
Connecting installs the Ankra agent in your cluster. The agent only makes outbound connections to Ankra, and Ankra sends work back over that same connection, so the cluster can sit behind a firewall, NAT or a private network. Nothing is opened inbound and Ankra holds no kubeconfig. It takes about five minutes.Before you start
- A payment method on the organisation. Without one the page shows Add a payment method before you connect a 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.” Add one under Plan and billing (Billing). Only the free playground runs without one.
- A role that may add clusters, and the
agents.managepermission to see the install command, because the command contains the agent’s access token. Roles and access lists the permissions. helmandkubectl, with a kubeconfig whose account may create a namespace and cluster-wide roles.- Outbound access from the cluster to
platform.ankra.app:443(the Ankra API),command.platform.ankra.app:4222(the channel Ankra sends work over, TLS) andregistry.ankra.cloud:443(the agent image and its chart).
1
Name the cluster
Open Infrastructure → Clusters and click Connect a cluster (
/next/clusters/import). The page Connect an existing cluster opens on the Install the agent tab.Fill in Cluster name (3 to 53 lowercase letters, digits and hyphens, starting with a letter) and answer What will this cluster run?: Production, Staging, Development, Testing, Local or Something else. Ankra treats changes on the cluster as carefully as this answer says, and never stops a production cluster at night. Click Get the install command.You should see the page change to Install the agent in my-cluster, with a Waiting for the agent to connect badge.2
Run the install command
Click Show the install command. The page shows two commands. Run the first to check which cluster your kubeconfig points at, because the install goes into that cluster:Then copy the second, Install the Ankra agent, exactly as shown and run it. It carries this cluster’s own token and pins the agent version, and has this shape:You should see Helm report the release
ankra-agent deployed in the namespace ankra.3
Check it is connected
The page watches for the agent, which usually reports in within a minute. Check now looks straight away.You should see the page turn into my-cluster is connected: “The Ankra agent is running in the cluster and reporting to Ankra.” Click Open the cluster. In Infrastructure → Clusters the cluster shows Online.
From the CLI
Write an ImportCluster file for the cluster and apply it with--wait. For a new cluster the CLI prints Cluster 'my-cluster' imported! and the agent install command under To install the Ankra agent, run:. Without --wait the command is not shown.
ankra cluster list, and Online in Infrastructure → Clusters.
What the agent installs
To see everything the chart would create without applying it:
When it does not connect
- The pod stays
Pendingor cannot pull its image: thedescribeoutput says why. - It keeps restarting: the logs say why.
- It runs and nothing arrives: the cluster cannot reach the three addresses under Before you start.
- Helm stopped with a permissions error: the account that ran it must be allowed to create a namespace and cluster-wide roles.
Remove it again
Removing the cluster in Ankra takes away the agent’s access at once and sends nothing to the cluster. The agent stays installed until you remove it:NotFound once it is gone:
Build a new cluster
Ankra Managed
Ankra creates the servers, private network and bastion on your own account, installs Kubernetes (kubeadm with Cilium by default, or k3s), and then operates it for you: upgrades, node groups, stop and start. The provider bills you directly. Creating one needs a payment method on your Ankra organisation.Hetzner
Hetzner Cloud servers in your Hetzner project.
OVHcloud
Public Cloud instances in your OVHcloud project.
UpCloud
Cloud servers in your UpCloud account.
DigitalOcean
Droplets in your DigitalOcean team.
Scaleway (Closed Beta)
Scaleway Instances in your Scaleway project.
AWS EC2
Self-managed Kubernetes on EC2 instances in your AWS account.
Proxmox VE
Virtual machines in your own Proxmox datacenter.
HPE Morpheus (Closed Beta)
Virtual machines through your Morpheus appliance.
Ankra Cloud (Closed Beta)
Servers Ankra runs for you, with no cloud account of your own.