Registering non-EKS clusters with EKS Connector¶
The EKS Console provides a single pane of glass to manage all your Kubernetes clusters, including those hosted on other cloud providers, via EKS Connector. This process requires registering the cluster with EKS and running the EKS Connector agent on the external Kubernetes cluster.
eksctl simplifies registering non-EKS clusters by creating the required AWS resources and generating Kubernetes manifests
for EKS Connector to apply to the external cluster.
To register or connect a non-EKS Kubernetes cluster, run
$ eksctl register cluster --name <name> --provider <provider> 2021-08-19 13:47:26 [ℹ] creating IAM role "eksctl-20210819194112186040" 2021-08-19 13:47:26 [ℹ] registered cluster "<name>" successfully 2021-08-19 13:47:26 [ℹ] wrote file eks-connector.yaml to <current directory> 2021-08-19 13:47:26 [ℹ] wrote file eks-connector-clusterrole.yaml to <current directory> 2021-08-19 13:47:26 [ℹ] wrote file eks-connector-console-dashboard-full-access-group.yaml to <current directory> 2021-08-19 13:47:26 [!] note: "eks-connector-clusterrole.yaml" and "eks-connector-console-dashboard-full-access-group.yaml" give full EKS Console access to IAM identity "<aws-arn>", edit if required; read https://eksctl.io/usage/eks-connector for more info 2021-08-19 13:47:26 [ℹ] run `kubectl apply -f eks-connector.yaml,eks-connector-clusterrole.yaml,eks-connector-console-dashboard-full-access-group.yaml` before <expiry> to connect the cluster
This command will register the cluster and write three files that contain the Kubernetes manifests for EKS Connector that must be applied to the external cluster before the registration expires.
list permissions for Kubernetes resources
in all namespaces to the calling IAM identity and must be edited accordingly if required before applying them to the cluster.
To configure more restricted access, see Granting access to a user to view a cluster.
To provide an existing IAM role to use for EKS Connector, pass it via
--role-arn as in:
$ eksctl register cluster --name <name> --provider <provider> --role-arn=<role-arn>
If the cluster already exists, eksctl will return an error.
To deregister or disconnect a registered cluster, run
$ eksctl deregister cluster --name <name> 2021-08-19 16:04:09 [ℹ] unregistered cluster "<name>" successfully 2021-08-19 16:04:09 [ℹ] run `kubectl delete namespace eks-connector` and `kubectl delete -f eks-connector-binding.yaml` on your cluster to remove EKS Connector resources
This command will deregister the external cluster and remove its associated AWS resources, but you are required to remove the EKS connector Kubernetes resources from the cluster.