☰

AWS EKS Discovery

This example demonstrates discovering existing EKS clusters in your AWS account.

The story comprises three features: * A Discovery blueprint * The Shared Cluster node type.

Prerequisites

This example expects the following prerequisites:

Cloudify CLI or Cloudify Management Console?

Cloudify allows for multiple user interfaces. Some users find the Cloudify Management Console (web based UI) more intuitive while others prefer the Cloudify CLI (Command Line Interface). This tutorial and all following ones will describe both methods.

Cloudify Management Console

This section explains how to run the above described steps using the Cloudify Management Console. The Cloudify Management Console and Cloudify CLI can be used interchangeably for all Cloudify activities.

Create Secrets

To connect to an infrastructure, a set of credentials are required. Cloudify recommends storing such sensitive information in a Cloudify secret. Secrets are kept encrypted in a secure way and used in run-time by the system. Learn more about Cloudify secrets here.

In this example, an infrastructure provider is selected during the blueprint installation. To ensure the correct secrets are created, use the following table to import the secrets for the provider selected.

Infrastructure Provider Example
AWS Infrastructure provisioning basics

To store the access keys as secrets in the Cloudify Manager, log in to the Cloudify Management Console and select the System Resources page. Scroll to the Secret Store Management widget and use the Create button to add the following new secrets:

Upload Plugins

Plugins are Cloudify’s extendable interfaces to services, cloud providers, and automation tools. I.e., connecting to AWS requires the AWS plugin.

To upload the required plugins to your manager, select the Cloudify Catalog page, scroll to the Plugins Catalog widget, and select the plugins you wish to upload.

For this example, upload the following plugins:

Upload Blueprints

A blueprint is a general purpose model for describing systems, services, or any orchestrated object topology. Blueprints are represented as descriptive code (yaml based files) and are typically stored and managed as part of the source repository. The Discovery blueprints are available here.

If you have installed an example before, the Discovery flow is slightly different.

The general flow required to set up a service consists of:

  1. Upload the blueprint describing a service to the Cloudify Manager.
  2. Create a deployment from the uploaded blueprint. This generates a model of the service topology in the Cloudify database and provides the “context” needed for running workflows.
  3. Run the install workflow for the created deployment to apply the model to the infrastructure.

For the Discovery and Batch Workload Management feature, this is the flow:

  1. Upload the blueprint describing an existing EKS Cluster to the Cloudify Manager.
  2. Upload the blueprint that enables us to scan your AWS Account for existing EKS clusters to the Cloudify Manager.
  3. Upload the blueprint that runs a Kubernetes workload on a Kubernetes Cluster managed in another Deployment Cloudify Manager.
  4. Create a deployment from the uploaded AWS Account blueprint. This generates a model of the service topology in the Cloudify database and provides the “context” needed for running workflows.
  5. Run the install workflow for the created deployment to apply the model to the infrastructure.
  6. Run the discover_and_deploy workflow from the “account” deployment to discover Kubernetes Clusters and install existing cluster deployments for them on the Cloudify manager.
  7. Run the batch_deploy_and_install workflow from the “account” deployment to install a Kubernetes workload on the discovered clusters.

Let’s run these, one by one.

Upload Existing Cluster Blueprint

To upload the Existing Cluster blueprint to the Cloudify Manager, select the Local Blueprints page, and use the Upload button.

Upload a Blueprint

Upload Account Blueprint

To upload the Account blueprint to the Cloudify Manager, select the Local Blueprints page, and use the Upload button.

Upload a Blueprint

Upload Kubernetes Workload Blueprint

To upload the Kubernetes Workload blueprint to the Cloudify Manager, select the Local Blueprints page, and use the Upload button.

Upload a Blueprint

Deploy & Install

Once the blueprints are uploaded, they will be displayed in the lueprints widget.

Upload a Blueprint

Create a new deployment from the “Account” blueprint.

To deploy the blueprint click the Create deployment button next to the “Account” blueprint. Specify a deployment name, update any inputs, and click Deploy & Install. Changing inputs is completely optional and the defaults are safe to use.

Create a Deployment

You will be directed to the Deployment page and will be able to track the progress of the execution.

The deployment you created should be displayed in the deployments list on the Deployments page.

Track the progress of a Workflow

Discovery and Deploy

Once the “Account” deployment is installed, you need to execute the “discovery and deploy” workflow.

Select the Execute workflow button.

This will open a drop down menu. Click on “AWS”, and then click on “discover and deploy”.

Execute workflow drop down

Click Execute.

Execute discover and deploy workflow

After the workflow complete, you should see all of the Kubernetes clusters in your account in the services list.

Services List