Platform administrationManage data plane clusters

Deregister a data plane cluster

Use this guide to remove a data plane cluster from your Astro Private Cloud (APC) control plane.

Only a System Admin can deregister a data plane cluster.

Prerequisites

  • Make sure there are no running Airflow Deployments in the data plane cluster.
  • Check that your automation configurations and scripts, such as your CI/CD or IaC, do not reference this cluster.

Deregister via the UI

  1. In the Astro Private Cloud UI, go to the Clusters page.
  2. Click See More […] on the cluster that you want to deregister.
  3. Click Deregister Cluster.
  4. Click Deregister.

Deregister a cluster

This removes the control plane association. Now, platform services no longer target this data plane cluster.

Deregistering a data plane cluster does not delete existing platform resources such as namespaces, services, or persistent volumes in your cloud environment. If you want to fully remove these resources, you must manually delete the Helm release.

Deregister through the Houston API

You can also deregister a data plane cluster by calling the deregisterCluster mutation on the Houston API. Send the request to https://houston.<your-base-domain>/v1 with a system service account or System Admin user token in the Authorization header. For details, see Authenticate to the Houston API.

1mutation {
2  deregisterCluster(id: "<cluster-id>") {
3    id
4    name
5  }
6}

Argument reference:

ArgumentTypeRequiredDescription
idUuidYesThe unique identifier of the cluster to deregister. Find it with the paginatedClusters query.

This permanently deletes the cluster record from the control plane. As with the UI flow, deregistration doesn’t delete platform resources running in the data plane Kubernetes cluster (namespaces, services, persistent volumes). Remove those by uninstalling the data plane Helm release.

Re-register a cluster

If you deregistered your data plane cluster by mistake, you can register the same data plane cluster again.