Clouds
AstroPulse creates clusters in your own cloud account: Amazon EKS on AWS, Google Kubernetes Engine (GKE) on Google Cloud, and Azure Kubernetes Service (AKS) on Azure, or self-hosted Kubernetes on virtual machines in AWS or Google Cloud. You pick the cloud and region on the first step of Create a cluster and how Kubernetes runs on the second. Every cluster runs in your account, on your bill, and AstroPulse reaches it with short-lived credentials from a connection you approve in that account; no cloud key goes in a cluster manifest.
Before you start
- An AWS account, a Google Cloud project, or an Azure subscription with a resource group that already exists.
- Permission in it to approve the connection: create a CloudFormation stack on AWS, run a setup script in Cloud Shell on Google Cloud, or run a setup script with the Azure CLI on Azure.
- Already run a cluster anywhere else? Register it instead.
In the console
-
Open New cluster and choose Bring your own account.
-
On Name and cloud, pick the Cloud and Region.
-
On Account, pick one under How Kubernetes runs. It lists what that cloud offers, each with its own summary and a Docs link to its page:
Open zoom view
| Cloud | How Kubernetes runs | Who runs what |
|---|---|---|
| Amazon Web Services | Amazon EKS | AWS runs the control plane; you choose the node groups and AstroPulse manages them in your account. |
| Self-hosted Kubernetes | AstroPulse builds Kubernetes on virtual machines in your account; the control plane runs on your machines, so you size both it and the workers. | |
| Google Cloud | Google Kubernetes Engine | Google runs the control plane; you choose the node pools, or use Autopilot and Google runs the nodes too. |
| Self-hosted Kubernetes | As on AWS. | |
| Microsoft Azure | Azure Kubernetes Service | Azure runs the control plane; you choose the node pools and AstroPulse manages them in your subscription. |
Each page has what its wizard asks for, the connect step, node groups, networking and versions: EKS, GKE, AKS, Self-hosted Kubernetes.
You should see
Once you pick how Kubernetes runs, Your cloud account opens under it: "The cluster is created in this account, and you pay your cloud for it directly." The next step, Connect, lets AstroPulse reach that account.
Choosing one
- A managed service (EKS, GKE, AKS) when you want the cloud to run the control plane. You size only the workers. Start here unless you have a reason not to.
- EKS Auto Mode or GKE Autopilot when you want the cloud to run the nodes as well: no node groups to size, and the cloud adds and removes machines as workloads need them.
- Self-hosted Kubernetes when you need control of the control plane itself, on AWS or Google Cloud. You size the control-plane node group as well as the workers.
EKS, GKE and AKS take GPU node groups on Kubernetes 1.36 or newer: GPU node groups. Self-hosted clusters take none.
Cloud accounts
Infrastructure › Cloud accounts lists every cloud account your organization connected or runs clusters in: one row per AWS account, Google Cloud project, or Azure subscription and resource group.
| Column | Meaning |
|---|---|
| Account | The cloud and the account. The account ID is hidden until you ask to see it, and only organization admins see it. |
| Status | Connected, Setting up, Not connected, Failed or Could not check. Hover for the reason AstroPulse gives. |
| Clusters | The clusters in that account, each with its state as the Kubernetes page shows it. |
| Pending connections | Connections whose cluster is not created yet, with the link's state: Linked, Setup in progress, Update needed or Setup failed. Open the account to see why one failed. |
| Regions | The regions the account's clusters run in. |
A connection belongs to one cluster, so you make it on the Connect step of New cluster, not on this page. Connections not checked in the last few minutes are checked again when the page loads. Clusters you registered yourself are listed below, under Clusters you run.
Only a failed or unfinished connection can be dismissed, and only by an organization admin. Dismissing removes the record from the list and changes nothing in your cloud account.
Kubernetes versions
The Kubernetes step lists the versions your cloud offers in the region, with AstroPulse default first: it sends no version, and the platform picks its own default. A version you type in a manifest can be short: <major>.<minor> picks the newest matching version the cloud offers (on GKE, in your release channel). A version that is not offered is refused.
| Cloud | Version format |
|---|---|
| Amazon EKS | major.minor or major.minor.patch |
| GKE | major.minor.patch or major.minor.patch-gke.NNNN |
| AKS | major.minor or major.minor.patch |
An EKS upgrade moves one minor version at a time, and the control plane cannot be rolled back. GKE also takes a release channel, and AKS an auto-upgrade channel and a node OS upgrade channel; their pages say what each does.
Other ways in
- Nova: ask it, for example "which cloud should I use for a GPU cluster in Europe?" or "which Kubernetes versions does EKS offer in us-west-2?".
- SDK and API: the clouds and what each offers come from the provisioner catalog; see the API reference.
With astroctl
# the versions each cloud offers, and what a cluster can upgrade to
astroctl cloud aws k8s-versions -r us-west-2
astroctl cloud gcp k8s-versions -r us-central1
astroctl cloud azure k8s-versions -r eastus
astroctl cloud aws k8s-versions --show-upgrade-paths
# every cloud account, its state and its clusters
astroctl cloud accounts list
astroctl cloud accounts list --include-failed -o json
# dismiss a failed or unfinished connection
astroctl cloud connections dismiss <connection-id>
<connection-id> stands for the ID cloud accounts list prints. Every flag: astroctl cloud.