EKS Cluster Management
Platform9 is able to connect to AWS and import existing EKS clusters, bringing them under management of Platform9 to enable centralized administration. Once a cluster has been imported into Platform9 you are able to:
- View EKS clusters alongside BareOS, Azure Native Clusters and AWS Native Clusters
- View and Edit RBAC configuration
- View and Managed Cluster Workloads
- Use the Application Catalog to deploy Helm 3 app
- Deploy Platform9 Monitoring
Import an EKS Cluster
To import an EKS cluster you must first create a service account for Platform9 in AWS, create an Access Key/Secret Key pair for the service account, grant the service account access to each EKS cluster and then create an AWS Cloud Provider within Platform9. Once the Cloud provider has been added you can import any EKS cluster that the Service Account has access to.
Steps to import EKS Cluster
- Within AWS create a service account for Platform9
- Generate and access key for the service account
- Grant the service account access to each EKS cluster
- Log into Platform9 and navigate to Infrastructure -> Cloud Providers tab
- On the Cloud Providers tab click "+ Add Cloud Provider"
- Provide a Name for the Cloud Provider and the Access Key Secret Key pair for the Service account and click next
- Once the Cloud Provider has been validated you can save the credentials to Platform9
- Validate the Cloud Provider has access to the regions you are running EKS clusters and then click Done
- Navigate to the Infrastructure -> Clusters tab and select 'Import' from the Add Cluster button
- Select AWS as the target cloud and click "Import EKS Cluster"
- Select the Cloud Provider configured with EKS Cluster Access and click Next
- Select each region where EKS clusters are running and select each cluster to be imported, several clusters can be imported in one action. Once all clusters are selected click next.
- Review the final list for import and click "Import"
- The imported clusters can be viewed on the Infrastructure -> Imported Clusters tab
Platform9 requires that the user that owns the Secret Key and Access Key be part of the "system: masters" group on each EKS cluster. We recommend that a service account be created within AWS and added to all EKS Clusters.