Skip to content

Convert to Managed

Imported Cluster Management is only supported for clusters with EKS as Kubernetes Cloud Provider. The cluster lifecycle management offers capabilities and controls to provision, expand, scale, upgrade and perform any post-provision operations on the imported EKS clusters.

The controller retrieves information on the imported EKS clusters to make the cluster’s infrastructure equivalent to the managed EKS clusters provisioned through the controller.


Requirement

The imported cluster lifecycle management for EKS must maintain the cluster status up-to-date at all times to make consistent changes to the cluster while performing the infrastructure operations


Convert To Managed

Users are allowed to convert the cluster to a Managed Cluster at any point in time through the controller

  • On successful EKS cluster import, a clickable label Convert to Managed is available next to the imported cluster as shown in the below example. Using this option provides a way for the users to communicate to the controller that an imported eks cluster is to be Managed by the platform henceforth.

Import Cluster

Clicking on the label, the below screen appears

  • Select the Cloud Credentials and Region of the imported cluster
  • Select the source cluster name from the provider to link to the imported cluster and click Convert to Managed Cluster

Import Cluster

The system shows the below message and the user must click Yes to confirm the conversion process

Import Cluster

Now the system saves the provided credentials against the cluster and changes the cluster type to EKS (based on provider). The managed and imported property is set to True. Cluster config gets generated for the cluster and declares the cluster is ready for performing post operations

  • On successful conversion, you will receive a success message as shown below

Import Cluster

Important

Currently, the self-managed nodegroups that exist in the imported EKS cluster (not created through controller) will not be considered for Day 2 operations.

You can see the cluster type as Imported + Managed and the list of operations allowed on the clusters page

Import Cluster


Nodegroup Availability

Once the conversion is complete, the details on Node Group, and Jobs are available for the users, similar to the other managed clusters

Import Cluster


Post Provision Operations

Following are the post provisioning (Day 2) operations supported on converted EKS clusters to managed:

  • Upgrade

    • Control Plane
    • Managed/self-managed Nodegroup (including custom amis)
  • Add

    • Managed/self-managed Nodegroup
  • Scale/Drain Managed and Self Managed Nodegroup

  • Update

    • Control Plane Endpoints
    • cloudwatchlogging
    • Control plane labels
    • Control plane tags
    • Rafay labels
    • Blueprints
    • Cloud providers
    • Node Taints and tags
  • Delete

    • Cluster
    • Managed Nodegroup
    • Self-managed Nodegroup

Limitations of Day 2 operation(s)

  • Imported clusters can contain both managed and self-managed nodegroups. If self-managed nodegroups are available in the imported cluster, they will not be visible in the controller
  • The post conversion nodegroup operations are supported on self-managed nodegroup created only through controller

Delete imported managed cluster(s)

When user deletes the imported managed cluster, the controller deletes the,

  • managed and self managed nodegroups created through controller and the underlying resources
  • managed nodegroups that got imported with the cluster and its underlying resources
  • EKS cluster itself

The below resources are not deleted:

  • The self managed nodegroups and their underlying resources that were not created through the controller
  • The underlying control plane resources (CloudFormation Stack, VPCs, etc.)

Refer IAM policy to know the required permission for the IAM role to convert the imported cluster to managed


RCTL to Convert EKS Imported Cluster(s)

Users can also use RCTL to convert the EKS imported clusters to managed clusters using the below command.

./rctl convert2managed cluster <controller-cluster-name>  --eks-cluster-name <source-cluster-name> --region <region-name> --credential <cred-name>