Agent Cloud

An opt-in deploy mode where Industric provisions a Kubernetes cluster for you and installs the operator into it automatically, so a deployment goes from created to running agents with no manual setup.

Agent Cloud is the shortest path to a cluster that runs your agents. Instead of installing the operator into a cluster you manage, you tick one box when you create a deployment and Industric provisions the cluster for you and bootstraps the operator into it automatically.

What it is

When you turn on Agent Cloud for a deployment, Industric provisions a managed Kubernetes cluster with a standard node size, installs the operator into it, and connects it to the control plane for you. There is no Helm to run, no deployment token to copy, and no manual connect step. Once provisioning finishes the deployment comes online like any other.

Create a deployment

In the dashboard, go to Deployments → New, name the deployment, then choose Use Agent Cloud. New deployments start with one standard node (2 CPU cores and 4Gi memory). CPU and memory are not editable. Your plan determines the total node allowance; check Usage for your limit.

Click Create & Provision to start provisioning.

The New deployment dialog with a Name field and two deployment targets, Use Agent Cloud (recommended, selected) and Own infrastructure, above a Create & Provision button — New deployment: name it, choose Use Agent Cloud as the deployment target, then Create & Provision.

Provisioning lifecycle

A new Agent Cloud deployment moves through a few states before it's ready. It shows a Provisioning… pill in the deployment list, and its detail page shows a panel in place of the usual agents and tools while the cluster is being built. This takes a few minutes.

State	What you see
pending	The deployment is queued; provisioning hasn't started yet.
provisioning	The Provisioning… pill; the cluster is being created and the operator installed.
ready	The operator connects and the deployment shows online, with its resource lists populated.
failed	The Provisioning failed pill; use Redeploy to try again.

A deployment detail page showing the Provisioning panel while the Agent Cloud cluster is created — While a deployment provisions, the detail page shows the status panel with Cancel provisioning available.

Manage the cluster

Once a deployment exists, you manage its cluster from the deployment detail page.

Resize. When the deployment is ready, the Resize cluster button lets you change the node count within your plan allowance. Each node keeps the standard CPU and memory size. Resize is available only in the ready state.
Redeploy. If provisioning failed, the status panel offers Redeploy to try again.
Cancel provisioning. While a deployment is still pending or provisioning, Cancel provisioning stops the attempt, tears down anything partially created, and leaves the deployment in the failed state so you can redeploy or delete it.
Delete. Deleting an Agent Cloud deployment tears down the provisioned cluster with it. This is automatic; there is no separate teardown step.

Redeploy rotates the token

Redeploy provisions a fresh cluster and issues a new deployment token for it. The previous token is discarded and can't be recovered. For Agent Cloud the token is managed for you, so there's nothing to re-copy, but any record you kept of the old one is no longer valid.

When provisioning fails

A failed deployment shows the reason on its status panel. The common ones, and what to do:

Message	What to do
A previous cluster for this deployment is still being cleaned up.	Wait a minute, then redeploy.
Provisioning timed out before the cluster was ready.	Redeploy to try again.
Not enough cluster capacity to provision right now.	Try again later.
Couldn't provision the Agent Cloud cluster.	Redeploy to try again, or contact support if it keeps failing.