Skip to main content
This guide walks the create form in the Ankra portal, which is the same for every provider. You end with a running Kubernetes cluster in your own cloud account, connected to Ankra and shown as Online. Each provider guide holds only what differs: the credential, the sizes, the locations and the provider’s own fields. Ankra managed means Ankra creates the servers, installs Kubernetes and upgrades it when you ask. Provider managed means the cloud provider runs the control plane, and Ankra creates the cluster and its node pools and connects it. Either way the cluster is created in your account and your provider bills you for it. On Proxmox VE and HPE Morpheus it runs on your own infrastructure, with no provider bill. Want to try Ankra without a cloud account? Start a free playground instead. Already running Kubernetes? Connect it instead.

Before you start

  • The clusters.create permission. Without it the page says “Your role does not allow creating clusters.” Ask an organisation owner for it. See Roles and access.
  • A payment method on the organisation. The review step warns “A payment method is required to create this cluster. Free credit does not replace it.” and the create is refused without one. See Credit and payment method.
  • A credential for the provider, with the permissions its credential page lists, for example Hetzner or AWS. You can also add it from inside the form.
  • An SSH key credential for the servers. You can add it from inside the form too. See SSH Key Credentials.
  • The provider enabled for your organisation. A provider your organisation cannot use is not listed. Opened by its address, the form says “<Provider> is not enabled for this organisation.”

Create the cluster

1

Open the create form

Go to Infrastructure → Clusters and click Add a cluster (/next/clusters/new).The page Add a cluster opens, with four steps across the top: Infrastructure, Configuration, Review and Provision.
2

Choose the provider

Under Where should the cluster run? (Or create a cluster with a provider when a free playground is offered), pick the provider card. A card with the GPU nodes badge offers GPU sizes.Where the provider offers both, Who runs Kubernetes on <provider>? follows. Pick Ankra managed or Provider managed. A provider with only one of them goes straight to the form.The form Add a <provider> cluster opens. An Estimated monthly cost card on the right fills in once you choose a credential and a location.
3

Name and purpose

Under Name and purpose, enter the Cluster name: 3 to 53 lowercase letters, digits and hyphens, starting with a letter. Some provider-managed services allow other characters or a shorter name; the hint under the field says which.Then answer What will this cluster run?: Production, Staging, Development, Testing, Local or Something else. Nothing is chosen for you, and the form will not go to review until you pick one. With Something else, name it under What it runs and choose How important is this cluster?. The answer changes defaults:
  • Development, Testing and Local start with one control plane node; Production and Staging start with three.
  • Ankra never stops a production cluster at night.
  • On UpCloud, the ingress load balancer plan starts larger for a production cluster.
Description is optional.
4

Where it runs

Under Where it runs, choose the <provider> credential - the account Ankra creates the cluster in. With none saved, click Add a credential; Add another credential adds one more.Choose the SSH key. It is installed on every server, so you can reach it over SSH through the management server. With none saved, click Add an SSH key.Choose the location (called Location, Region or Zone, depending on the provider). Some providers ask more questions here, such as the size of the internet gateway; the provider guide explains them.The Control plane, Worker nodes and Kubernetes sections appear once the location’s sizes are read.
5

Control plane

A Provider managed form has no control plane or management server to size: the provider runs them. Its provider guide covers the fields it has instead.Under Control plane nodes, pick Single node (lower cost, cluster changes pause if it goes down) or High availability (three nodes, recommended for production). Choose the Control plane size.Expand the Management server row (Gateway on OVHcloud) to change its size. It is the cluster’s SSH entry point: Ankra and your SSH sessions reach the other servers through it, and they take no SSH from outside the cluster’s network.Each size field offers Sizes (Small, Medium, Large, X-large) or Exact server type, the provider’s full list with prices. GPU types are listed in Exact server type only.
6

Worker nodes

Under Worker nodes, each node group is a set of nodes of the same size. Set its Group name, Nodes and size. Add a node group adds another, up to the provider’s limit.
  • Placement, labels and taints adds node labels (Add node label) and taints (Add taint) and, on OVHcloud, UpCloud and AWS, Pin to availability zone.
  • Scale this group automatically sets At least and At most (up to 100) nodes. See Cluster autoscaling. The box is not offered for Proxmox VE, HPE Morpheus or UpCloud Managed Kubernetes groups: UpCloud Managed Kubernetes refuses autoscaling on a node pool.
7

Kubernetes

Under Kubernetes, keep kubeadm (upstream Kubernetes with the Cilium network plugin, recommended for production) or pick k3s (lighter, for small and development clusters). With k3s, a Network plugin field appears. Choose the Kubernetes version.The distribution, the network plugin and the etcd layout cannot be changed after create. See Choices fixed at create time.
8

Cluster configuration in Git (optional)

Under Cluster configuration in Git, tick Keep the configuration in a Git repository and choose the Git connection, the Repository and the Branch. Ankra then keeps the cluster’s Stacks and add-ons as files in that repository. Only GitHub and Bitbucket Cloud connections are listed.With no Git connection, the section says “No Git connection is set up, so Ankra keeps the configuration itself.” You can add a repository later in the cluster’s settings. See GitOps.
9

Advanced configuration (optional)

Expand Advanced configuration for:
  • Private network range - leave it empty for the provider’s default.
  • Addresses allowed to reach the management server - IPv4 addresses or ranges, separated by commas. Leave it empty to allow SSH from any address. On Scaleway the field is Addresses allowed to reach the gateway, and empty keeps the Scaleway default. On Ankra Cloud the cluster the form creates is IPv6-only, so these IPv4 entries do not apply; see Ankra Cloud Clusters.
  • Run etcd on separate nodes (kubeadm only) - pick 3 nodes or 5 nodes and the etcd node size.
  • Install the networking stack - an ingress controller and load balancer, so applications can receive traffic from the internet. On by default.
  • Add the Kubernetes Gateway API - shown with the networking stack. See Gateway API.
  • Give the cluster a public domain - a domain under ankra.cc with automatic DNS records and TLS certificates. On by default. See Use your own domain for a domain of yours.
  • Provider sections, such as AWS network or UpCloud zone placement, described in the provider guide.
10

Review the cluster

Click Review cluster. A field that still needs an answer is listed at the top of the form, for example “Choose what this cluster will run.”The page Review <cluster name> lists the Settings, the server count and the cost estimate. Under Checks before creating, Ankra runs its checks right away. Where the provider supports it, Ankra asks the provider whether the account can create this cluster.
  • “All checks passed.” means you can go on.
  • A failed check names what to change. Click Back to configuration, fix it, then review again. Run the checks again reruns checks that could not run.
  • A missing payment method shows as a warning here; the create itself is refused.
11

Create the cluster

Click Create cluster.The page Creating <cluster name> shows three stages: Create infrastructure, Set up Kubernetes and Connect to Ankra. You can leave the page; setup continues. View operation opens the operation with every task.When setup finishes, the page reads <cluster name> is ready. Click Open the cluster.

Verify

  1. In Infrastructure → Clusters, the cluster’s status reads Online. While it is being set up, it reads In progress, and the badge beside its name on its own pages reads Provisioning.
  2. Point kubectl at it through Ankra and check the nodes. This needs a Cluster Access grant.
    Every control plane and worker node is Ready.

What the form does not set

These choices have no field in the form. Use the CLI or the API when you need them at create time:

What can go wrong

Next steps