Docs / Building infrastructure
The assistant
Ask for a cluster, or a change to one, in plain terms, and approve the plan it produces.
The assistant turns a conversation into a cluster specification, plans it with Terraform against your account, and puts the plan in front of you to approve. It asks only for what it cannot infer and shows the settings it recorded beside the conversation, so you can check them before anything is planned.
What it can do
| Ask it to | Example |
|---|---|
| Build a cluster | “A small dev cluster on AWS in Ireland with metrics and logs.” |
| Change a cluster | “Add ingress and certificates to staging-eu.” |
| Resize a cluster | “Let staging-eu scale to six nodes.” |
| Upgrade Kubernetes | “Move staging-eu to the next Kubernetes version.” |
| Rename, inspect or list | “What is running on staging-eu?” |
| Tear a cluster down | “Tear down staging-eu.” |
| Deploy an application | “Deploy storefront to preview.” |
| Promote an application | “Deploy storefront to live.” |
It works with Amazon EKS clusters in your connected AWS accounts. It does not create databases, buckets or other resources on their own.
Deploying from a conversation
Asked to deploy to the first environment, the assistant shows a card with the application, the environment and its cluster, the branch, and the image it would replace. Start deployment builds it straight away, as Deploy does on the Deployments page.
Asked to deploy to a later environment, it asks which build to move from the environment before it, listing them by commit with their scans. The card then promotes that exact image without rebuilding it. Where the environment requires approval, Request approval sends it to Approvals, and nothing happens until someone else approves it.
Each card expires after a few minutes. Cancel, or let it expire, and nothing is deployed.
Writing a good request
- Name the cloud account if you have more than one.
- Give the region in words or as a code: “Ireland” and
eu-west-1both work. - Say what the cluster is for. The assistant suggests a node size and count from that, and tells you what it chose.
- Name the capabilities you want, such as metrics, logs or ingress. See Cluster capabilities.
Approving in time
A plan takes a few minutes to produce. Once it is ready, its approval expires after a few minutes more; after that the Approve button is withdrawn and only Reject remains. To go ahead after an expiry, start a new conversation and state every setting in one message, and the assistant plans it again.
What it cannot do
It cannot change your cloud on its own. A change becomes a plan, policy checks the plan, and a person approves it. The assistant acts with your permissions, so it cannot propose anything you could not do yourself.