In Part-1, you will configure and provision an Amazon EKS Cluster
Step 1: Configure RCTL¶
This step is a one-time task. In this step, you will download the RCTL CLI so that you can interact with your Org programmatically and embed all operations in your existing automation platform.
- Login into your Org and click on My Tools
- Download the RCTL CLI binary for your operating system and install it on a node from which you can perform Kubectl operations to your EKS-A cluster.
- Download the CLI config and initialize the RCTL CLI with the config file
./rctl config init <full path to config file>
Optionally, check if RCTL is properly configured and can interact with your Org. You should see an output similar to the example below.
./rctl get projects NAME defaultproject
Step 2: Provision EKS cluster¶
This step assumes the following:
- You have already created "cloud credentials" in the "default project".
- You have configured the RCTL CLI to interact with "default project".
In the example below, you will provision an Amazon EKS cluster in the "default project" with "one managed nodegroup" using the cluster specification provided below.
|Node Group Type||Managed|
kind: Cluster metadata: name: amp-demo project: default spec: type: eks cloudprovider: qa-eks blueprint: default --- apiVersion: rafay.io/v1alpha5 kind: ClusterConfig metadata: name: amp-demo region: us-west-1 version: "1.20" managedNodeGroups: - name: managed-ng1 instanceType: t3.large desiredCapacity: 2
- Copy the cluster specification and save it to a YAML file (e.g "amp-demo.yaml")
- Use the RCTL CLI to provision the EKS cluster in your project
./rctl apply -f "amp-demo.yaml"
This will start the provisioning of an EKS cluster in the project. This step can take ~10-15 minutes to complete. Once provisioning is successful, you should be able to interact with your EKS cluster in your Project.
You are now ready to move on to the second part of the recipe.