Import Cluster Template
The "AWS EKS Environment Provider From Existing Cluster" template allows you to set up an EKS runtime for Harmonix that uses a preexisting EKS cluster.
Here are the 2 main uses:
- Use a cluster you had set up in the past, before adopting Harmonix.
- Continue using whatever mechanism you prefer to provision your EKS clusters (outside of Harmonix).
Whatever your reason, using this template will allow you to use prexisting clusters as part of an Harmonix EKS Environment Provider.
This template only "imports" EKS clusters for use by an EKS Environment Provider. It does NOT import any applications that are running in an imported cluster that were created outside of Harmonix.
Screenshot of the AWS EKS Environment Provider From Existing Cluster Template:
How Is This Template Different From The AWS EKS Environment Provider Template?
This template performs a subset of what the "AWS EKS Environment Provider" template does. Please see the AWS EKS Environment Provider template documentation for a detailed list of features. The purpose of this template is to use an existing EKS cluster, but to also create the Harmonix-specific infrastructure that is needed in order for Harmonix to use the cluster as part of an EKS Environment Provider.
If you use the "AWS EKS Environment Provider From Existing Cluster" template, the following will NOT be created/configured:
- VPC
- EKS Cluster
- FluentBit log forwarding
- Security Groups
- OIDC Provider for service accounts
- IAM Roles
- aws-auth ConfigMap settings
Choosing to use a cluster that is created outside of Harmonix means that you are responsible for configuring your cluster to be compatible with Harmonix. See the AWS EKS Environment Provider template documentation for details on what Harmonix expects to be set up for a cluster.
Optional Components
The following will only be created if you answer "Yes" to "Create Harmonix Resources In EKS Cluster?"
- "opa-cluster-admin" ClusterRoleBinding
- ClusterRole for viewing/listing namespaces