Find your message
A payment method for clusters
What you see. On Infrastructure → Clusters → Connect a cluster, the warning 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.” Creating a cluster stops on its review step with A payment method is required to create this cluster. Why. A pay-as-you-go organisation with no usable payment method is on the free tier. It may not create clusters, connect clusters or order paid playgrounds, whatever credit it holds. The free trial playground is the one cluster it can start. How to clear it. An organisation owner opens Settings → Plan and billing (/next/organisation/billing#unlock) and, under Unlock paid usage, clicks Add payment method. The card is added with Stripe, and the browser comes back to the page. Then try again. Someone who cannot add it reads “Ask someone who manages billing for your organisation to add one.” on the connect page.
The free allowance without a payment method
What you see. A pipeline run that did not start is marked Did not start: add a payment method. Its notice, Run did not start: add a payment method, has an Open billing button. Why. A Pay as you go organisation without a payment method gets a small free allowance each calendar month (UTC):
Both are checked when a run or a request starts, so the one that crosses the line finishes and the next is refused. Once the pipeline minutes are spent, every new run is refused, wherever its steps would have run, because Ankra decides where a step runs after the run is queued.
How to clear it. Add a payment method under Settings → Plan and billing. Saving it lifts the free tier and its allowance together. Then run the pipeline again.
The 30-vCPU trial limit
What you see. “The 30-vCPU trial limit would be exceeded. An organisation owner must approve paid usage in Plan and billing before adding capacity.” Or, when Ankra cannot count: “Capacity could not be verified against the 30-vCPU trial limit. Refresh the provider catalogue and cluster observations, or ask an organisation owner to unlock paid usage.” Why. On the Free or Homebuilder plan, until an owner approves paid usage, Ankra refuses to create or grow a cluster it builds for you when the organisation’s clusters would then run more than 30 vCPUs. The limit is checked whenever such a cluster grows, from the portal, the API, GitOps or the autoscaler. Connecting a cluster is not refused by it, but a connected cluster’s vCPUs count toward the 30. A payment method alone does not lift it. An organisation on Pay as you go, Startup or Enterprise never meets this limit: your plan shows under Settings → Plan and billing. How to clear it. An organisation owner opens Settings → Plan and billing and goes to Unlock paid usage. The section shows the prices. Add a payment method if there is none, tick the box that approves the prices and authorises paid usage and removal of the 30-vCPU trial limit, and click Confirm charges and unlock. Anyone else reads Only an organisation owner can approve charges and unlock the account. Billing explains the prices and what they cover.Ankra AI stops answering
What you see, in Ask Ankra:A pipeline waits for approval
What you see. TheAnkra pipeline check on a pull request reads Awaiting authority approval, and the organisation gets a notification Pipeline authority approval needed: my-org/my-repo (…).
Why. A pull request may change what a pipeline does, but not what it may touch: secrets, credentials, caches, CPU and memory, timeouts, services, network access and where a step runs. Those protected settings take effect only once an administrator approves the definition on the default branch. Until then the run is skipped, if a stage depends on them, or runs with the last approved settings.
How to clear it. An administrator approves the settings on Build & delivery → Builds and clusters, under Pipeline settings waiting for approval. The steps are in Get started with Ankra CI. Approving needs a person: a service-account token, or Ankra AI acting through one, is refused with “A pipeline definition’s authority can only be approved by a human administrator”.
Two-step sign-in
Tokens. On API access in your account, the row Add a second step to sign in first takes the place of the Create token button until your account has two-step sign-in. The portal asks for it because a token acts as you. Click Set up two-step sign-in, which opens Sign-in and security in your account, add a passkey or an authenticator app, and come back. Service tokens covers tokens for automation. Organisations that require it. When an organisation requires a second step, signing in stops at Set up two-step sign-in to continue: “Your organisation requires a second step after you sign in, on top of your password or sign-in provider.” Choose Passkey or Authenticator app. You get recovery codes in case you lose your device. While the organisation requires it, you cannot remove your last authenticator: “Your organisation requires MFA, so you cannot remove your last authenticator”. Account security has the details.Your role
Roles and access lists what each role may do.
Where to go next
- Billing: plans, prices and the payment method.
- Find your way around Ankra: where each page in this guide lives.