Skip to content


In this exercise, you will learn how to use the controller to configure and provision an Amazon EKS Cluster with Custom Networking. You will then deploy a containerized application to the EKS cluster with the pods getting deployed to the host and pod network.

What Will You Do by Part

Part What will you do?
1 Configure and Provision an AWS EKS Cluster with Custom Networking
2 Deploy a Workload using Custom Networking
3 Deprovision the EKS cluster

You can also watch a video describing this below.


  • You have access to an Amazon AWS account with privileges to create an IAM Role with the default Full IAM Policy to allow provisioning of resources on your behalf as part of the EKS cluster lifecycle. Steps to create the IAM Role can be found here.
  • You have installed and configured the RCTL CLI so that you can perform the tasks with automation and declarative cluster specification files.
  • You have created a Cloud Credential using the ARN of the AWS IAM Role created above in the project "defaultproject".
  • You have attached a secondary CIDR block from the or ranges to your VPC.
  • You have created subnets from the secondary CIDR block.

VPC Configuration

Use the following VPC configuration as a reference to the following cluster spec.

Name Subnet-Id CIDR AZ
SecondarySubnetPrivateUSWEST2A subnet-081ff5e370607fafa us-west-2a
SecondarySubnetPrivateUSWEST2B subnet-0d336d3350d55a986 us-west-2c
SecondarySubnetPrivateUSWEST2D subnet-0a4548dabae4b34cb us-west-2d
PrimarySubnetPrivateUSWEST2A subnet-083bf5944d5ecb3dd us-west-2a
PrimarySubnetPrivateUSWEST2B subnet-0bce0fb4a1f682e13 us-west-2c
PrimarySubnetPrivateUSWEST2D subnet-0f4534f41b98dd7be us-west-2d
PrimarySubnetPublicUSWEST2A subnet-0ad39284a3ed57cfe us-west-2a
PrimarySubnetPublicUSWEST2B subnet-0238aec96d29bc809 us-west-2c
PrimarySubnetPublicUSWEST2D subnet-0fb450e17506bd15d us-west-2d