Skip to content

Deploy Workload

What Will You Do

In this part, you will configure and deploy a workload to the EKS cluster in a specific namespace called "dev". The workload will create two deployments with one of the deployments running on the host network and the other running on the pod network.

Create Namespace

As a user with appropriate RBAC (i.e. Org Admin or Infra Admin or Workspace Admin), create a namespace on the EKS cluster.

  • Click on Infrastructure -> Namespaces
  • Click on Create New Namespace
  • Select "dev" for name and "wizard" for type
  • Select the EKS Cluster for placement and publish the namespace to the remote cluster


For this exercise, we will keep it simple and skip the assignment of resource quotas and policies.

Configure & Deploy Workload

As a user with appropriate RBAC (i.e. at least Project Admin or Namespace Admin), we will create a workload to deploy to our remote EKS cluster.


Download the provided YAML file and save it to your computer. We will deploy this to the cluster.

  • Under Applications -> Workloads, create a "New Workload"
  • Enter the name "debug" for the workload
  • Select "k8s yaml" for type
  • Select "upload files manually"
  • Ensure the namespace from the prior step is selected

Configure Workload

  • In the upload step, upload the file "debug.yaml" and click on "Save and Go To Placement"
  • In placement, select the name of the EKS cluster and "Save and Go To Publish"
  • Publish the workload

Workload Publish In Progress

The controller will take the provided YAML manifest and create two deployments running in the "dev" namespace.

Verify Custom Networking

In our simple example, one deployment is using the host network which runs on the primary CIDR and the other deployment uses the pod network which runs on the secondaryt CIDR.

Verify Pods

  • In our workload, Click on Debug to bring up the integrated Kubernetes resources dashboard.
  • Click on Pods on the left
  • You should see two pods with IP Addresses from the different CIDR blocks

Debug Pod Status