Ocean Creation
Importing of an existing Kubernetes cluster
AWS EKS
In this section, we will import the EKS cluster that we just created into Spot Ocean.
Let’s start by logging into the Spot Console, and clicking on the “Hamburger” button in the top left to display all the Spot by Netapp products. Then select Ocean and navigate to Cloud Clusters.
Then select Connect an Existing EKS Cluster and click the blue continue button.
Then select the region you created your EKS cluster in (US-East-2) in our case. The Spot by Netapp IAM role that you created in your AWS account allows us to read the metadata about your cluster and populate them here.
Once you selected your cluster, the “Ocean Cluster Name” will automatically populate and you can proceed to the next page. This will prompt you to select a node group from your existing EKS cluster. This node group will serve as our template to begin launching infrastructure within Ocean. Once you select the node group, click “Next”
This page confirms that we will be importing a single node group pre-created from eksctl. You can proceed to the next page (Connectivity) without any changes.
Once you reached the connectivity page, this is where we will deploy our Spot Ocean controller into our EKS cluster. The Ocean controller is responsible for faciliating communication between our K8s cluster and the Spot by Netapp SaaS layer. We can start by generating a programmatic token (any name will do), and once we confirm it will help populate a script with the token included that we can copy and paste into our Cloud9 IDE which has already been set to our EKS clusters' kube-context.
Now navigate back to our Cloud9 IDE and paste the script below:
Within a minute or two you should see that the Ocean controller was successfuly deployed. If you encounter any errors you should double check you copied the entire bash script.
Now navigate back to the Spot Ocean console and click “Test Connectivity.” This test ensures the Ocean controller has successfuly communicated back to our SaaS layer. You might need to wait up to two minutes before this is successful.
One you see the green check mark that the Ocean controller is running you can proceed to the next page. If you receive an error about the controller not yet running, allow up to two minutes before testing connectivity again.
This final review show you the final configuration that we will use to create our Ocean cluster. Once complete you can click Create.
Once the cluster creates successfuly, we should see an overview page that will begin populating once we begin receiving more data from EKS.
As a last check, let’s navigate to the “Nodes” tab of the Ocean cluster
We should see a node created from Ocean within 1-2 minutes. As long as the node has a “Node Name” and we can see Resource Allocations, that confirms the node Ocean launched has registered to EKS successfuly. We can now proceed to the next part of the lab.