Deregistering a cluster - Amazon EKS
To deregister the Kubernetes clusterTo clean up the resources in your Kubernetes cluster
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Help improve this page

Want to contribute to this user guide? Scroll to the bottom of this page and select Edit this page on GitHub. Your contributions will help make our user guide better for everyone.

Deregistering a cluster

If you are finished using a connected cluster, you can deregister it. After it's deregistered, the cluster is no longer visible in the Amazon EKS console.

You must have the following permissions to call the deregisterCluster API:

  • eks:DeregisterCluster

  • ssm:DeleteActivation

  • ssm:DeregisterManagedInstance

This process involves two steps: Deregistering the cluster with Amazon EKS and uninstalling the eks-connector agent in the cluster.

To deregister the Kubernetes cluster

Amazon CLI
Prerequisites

  • Amazon CLI must be installed. To install or upgrade it, see Installing the Amazon CLI.

  • Ensure the Amazon EKS Connector agent role was created. .

Deregister the connected cluster.

aws eks deregister-cluster \
    --name my-cluster \
    --region region-code
Amazon Web Services Management Console

  1. Open the Amazon EKS console at https://console.amazonaws.cn/eks/home#/clusters.

  2. Choose Clusters.

  3. On the Clusters page, select the connected cluster and select Deregister.

  4. Confirm that you want to deregister the cluster.

eksctl
Prerequisites
To deregister your cluster with eksctl

To clean up the resources in your Kubernetes cluster

Helm

  • Run the following command to uninstall the agent.

    helm -n eks-connector uninstall eks-connector
YAML manifest

  1. Delete the Amazon EKS Connector YAML file from your Kubernetes cluster.

    kubectl delete -f eks-connector.yaml

  2. If you created clusterrole or clusterrolebindings for additional IAM principals to access the cluster, delete them from your Kubernetes cluster.