Deregister a Kubernetes cluster from the Amazon EKS console - Amazon EKS

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.

Deregister a Kubernetes cluster from the Amazon EKS console

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.

Deregister the Kubernetes cluster

To deregister a cluster from Amazon EKS connector, you can use one of these tools:

AWS CLI

  1. AWS CLI must be installed. To install or upgrade it, see Installing the AWS CLI.

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

  3. Deregister the connected cluster.

    aws eks deregister-cluster \ --name my-cluster \ --region region-code

AWS Management Console

  1. Open the Amazon EKS console.

  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

  1. Install eksctl version 0.68 or later. To install or upgrade it, see Get started with Amazon EKS – eksctl.

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

  3. Deregister the connected cluster:

    eksctl deregister cluster --name my-cluster

Clean up the resources in your Kubernetes cluster

To uninstall the eks-connector agent, use one of the following tools:

helm

Run the following command to uninstall the agent.

helm -n eks-connector uninstall eks-connector

yaml

  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.

πŸ“ Edit this page on GitHub