Amazon Elastic Kubernetes Service (EKS)
The Cloud Provider Cluster Support features enable users to create and delete a new Amazon Elastic Kubernetes Service (EKS) cluster in Nirmata.
How to Manage an EKS Cluster in Nirmata
To manage an EKS Cluster in Nirmata, add Amazon as a Cloud Provider in Nirmata. A valid Amazon Web Services account and credentials is required.
See AWS Cloud Provider for full documentation on adding Amazon as a Cloud Provider.
IMPORTANT: When adding Amazon as a Cloud Provider be sure to note the Account ID provided by Nirmata. The Account ID is required when creating an EKS Cluster.
In addition to adding AWS as a Cloud Provider in Nirmata, the following must be installed on the local machine:
- aws-iam-authenticator for Amazon EKS
If using Ubuntu 16.04 AM or any other Linux images enable the following configurations:
sudo iptables -P INPUT ACCEPT sudo iptables -P FORWARD ACCEPT sudo iptables -P OUTPUT ACCEPT
Then ensure that the Security Group allows all ports between the hosts and their respective subnet. If enabling TCP Elastic Load Balancing (ELB), the connection must listen for requests port 443 and target the group for 6443.
Create a EKS Cluster
To add an EKS Cluster in Nirmata, select Clusters from the sidebar menu and then click the +Add Cluster button.
Select Create EKS Cluster and click Complete Setup.
In addition to adding AWS as a Cloud Provider, managing an EKS Cluster in Nirmata requires a second role in AWS.
To create the second role required for EKS Cluster management in Nirmata, login to the AWS Management Console and select IAM Services.
Select Roles and then click on the button to Create Role.
Select Another AWS Account.
Enter the Account ID provided by Nirmata during the AWS Cloud Provider setup.
Apply the following policies to the role:
Locate each permission by entering the Permission Name into the Search box. Place a checkmark next to each required permission. After adding all permissions, click the Create Policy button.
Complete the role creation process. Be sure to note the Access Keys (Access Key IDs and Secret Access Keys).
Copy the Role ARN from the Role Summary screen in AWS.
In Nirmata, complete the first page of Cluster Configuration Details. Paste the Role ARN from AWS into the Cluster Role ARN field. Click Next.
On the second Cluster Configuration Details page, enter the remaining information. Choose a customized Image ID created in AWS or use one of Amazon’s EKS-Optmized AMI image IDs. After completing all of the fields, click Create Cluster.
In 20 to 25 minutes, the new Cluster is visible in Nirmata and in the AWS dashboard.
When the cluster is visible in Nirmata, the following three (3) YAML files will be available for download and installation. * nirmata-aws-config.yaml * nirmata-aws-auth.yaml * nirmata-kubernetes-controller.yaml
Download and install each YAML to place nodes in ready-state and connect the cluster to Nirmata.
Delete a EKS Cluster
NOTE: All Applications and Environments running inside the cluster must be stopped and deleted before deleting the cluster.
To delete an EKS Cluster, navigate to the cluster from the Cluster menu.
From the Settings menu, select Delete Cluster.
Enter the Cluster name and click Delete.
The cluster is deleted in Nirmata and AWS.