Clusters¶
Overview¶
Infrastructure -> Clusters
is for creating and managing Kubernetes Clusters, Morpheus manager Docker Clusters, KVM Clusters, or Cloud specific Kubernetes services such as EKS. The Combo Cluster is a combination Kubernetes, KVM and Functions* Cluster, with all nodes supporting all three provision types.
Cluster Types¶
Name |
Description |
Supported Clouds |
Provider Type |
Kubernetes Cluster |
Provisions by default a Kubernetes cluster consisting of 1 Kubernetes Master and 3 Kubernetes Worker nodes. Additional system layouts available including Master clusters. Custom layouts can be created. |
All |
Kubernetes |
Docker Cluster |
Provisions by default a Morpheus controlled Docker Cluster with 1 host. Additional hosts can be added. Custom layouts can be created. Existing Morpheus Docker Hosts are automatically converted to Clusters upon 4.0.0 upgrade. |
All |
Docker |
EKS Cluster |
Provisions a EKS master and 3 EC2 worker node. |
AWS |
Kubernetes |
AKS Cluster |
Azure |
Kubernetes |
|
KVM Cluster |
Provisions by default a Morpheus controlled KVM Cluster with 1 host. Additional hosts can be added. Custom layouts can be created. Existing Morpheus KVM Hosts are automatically converted to Clusters upon 4.0.0 upgrade. |
VMware, Bare Metal |
KVM |
Combo Cluster |
Provisions by default a Morpheus controlled Docker, VM and Functions* Cluster with 1 host. Additional hosts can be added. |
VMware, Bare Metal |
Morpheus |
Ext Kubernetes |
Brings an existing (brownfield) Kubernetes cluster into Morpheus |
All |
Kubernetes |
Requirements¶
Morpheus Role permission
Infrastructure: Clusters -> Full
required for Viewing, Creating, Editing and Deleting Clusters.Morpheus Role permission
Infrastructure: Clusters -> Read
required for Viewing Cluster list and detail pages.
Cluster Permissions¶
- Cluster Permissions
Each Cluster has Group, Tenant and Service Plan access permissions settings (“MORE” > Permissions on the Clusters list page).
- Namespace Permissions
Individual Namespaces also have Group, Tenant and Service Plan access permissions settings
Kubernetes Clusters¶
Requirements¶
Agent installation is required for Master and Worker Nodes. Refer to `Morpheus Agent`_ section for additional information.
- Access to Cloud Front, Image copy access and permissions for System and Uploaded Images used in Cluster Layouts
Image(s) used in Cluster Layouts must either exist in destination cloud/resource or be able to be copied to destination by Morpheus, typically applicable for non-public clouds. For the initial provision, Morpheus System Images are streamed from Cloud Front through Morpheus to target destination. Subsequent provisions clone the local Image.
System Kubernetes Layouts require Master and Worker nodes to access to the following over 443 during K8s install and configuration:
Morpheus Role permission
Infrastructure: Clusters -> Full
required for Viewing, Creating, Editing and Deleting Clusters.Morpheus Role permission
Infrastructure: Clusters -> Read
required for Viewing Cluster list and detail pages.
Creating Kubernetes Clusters¶
Provisions a new Kubernetes Cluster in selected target Cloud using selected Layout.
System (Morpheus provided) Kubernetes Layouts:
Cluster Type Name |
Description |
Code |
---|---|---|
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in xen |
kubernetes-1.20.2-ubuntu-18.04.5-xen-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in scvmm |
kubernetes-1.20.2-ubuntu-18.04.5-scvmm-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in opentelekom |
kubernetes-1.20.2-ubuntu-18.04.5-opentelekom-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 |
kubernetes-1.20.2-ubuntu-18.04.5-nutanix-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in manual |
kubernetes-1.20.2-ubuntu-18.04.5-morpheus-amd64-single |
External Kubernetes 1.20 |
Connect to an external kubernetes cluster. |
kubernetes-external-1.20 |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in hyperv |
kubernetes-1.20.2-ubuntu-18.04.5-hyperv-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in Huawei |
kubernetes-1.20.2-ubuntu-18.04.5-huawei-amd64-single |
Kubernetes 1.20 Cluster AKS |
This 20 provision a single kubernetes master in Azure |
kubernetes-azure-aks-1.20 |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in Openstack |
kubernetes-1.20.2-ubuntu-18.04.5-openstack-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 |
kubernetes-1.20.2-ubuntu-18.04.5-google-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 |
kubernetes-1.20.2-ubuntu-18.04.5-amazon-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in vmware |
kubernetes-1.20.2-ubuntu-18.04.5-vmware-amd64-single |
MKS Kubernetes 1.20 Cluster on Ubuntu 18.04 |
provision a kubernetes 1.20 cluster on ubuntu 18.04 in fusion |
kubernetes-1.20.2-ubuntu-18.04.5-fusion-amd64-single |
Kubernetes 1.18 Cluster AKS |
This will provision a single kubernetes master in Azure |
kubernetes-azure-aks-1.18 |
Kubernetes 1.17 Cluster EKS |
This will provision a single kubernetes master in amazon with weave and openebs |
kubernetes-amazon-eks-1.17 |
Kubernetes 1.17 HA Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in xen with weave and openebs |
kubernetes-1.17-xen-ubuntu-16.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in xen with weave and openebs |
kubernetes-xen-1.17-ubuntu-16.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in scvmm with weave and openebs |
kubernetes-scvmm-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in scvmm with weave and openebs |
kubernetes-scvmm-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in openstack with weave and openebs |
kubernetes-openstack-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in openstack with weave and openebs |
kubernetes-openstack-ubuntu-18.04-single |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in opentelekom with weave and openebs |
kubernetes-opentelekom-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in nutanix with weave and openebs |
kubernetes-nutanix-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 HA Cluster on Linux, Weave, OpenEBS |
This will provision a kubernetes cluster with weave and openebs |
kubernetes-1.17-morpheus-linux-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Linux, Weave, OpenEBS |
This will provision a single kubernetes master with weave and openebs |
kubernetes-1.17-morpheus-linux-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in hyperv with weave and openebs |
kubernetes-hyperv-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in hyperv with weave and openebs |
kubernetes-hyperv-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in huawei with weave and openebs |
kubernetes-huawei-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in huawei with weave and openebs |
kubernetes-huawei-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in google with weave and openebs |
kubernetes-google-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in google with weave and openebs |
kubernetes-google-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in esxi with weave and openebs |
kubernetes-esxi-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in esxi with weave and openebs |
kubernetes-esxi-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in digitalOcean with weave and openebs |
kubernetes-digitalOcean-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in digitalOcean with weave and openebs |
kubernetes-digitalOcean-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in azure with weave and openebs |
kubernetes-azure-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in azure with weave and openebs |
kubernetes-azure-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in amazon with weave and openebs |
kubernetes-amazon-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in amazon with weave and openebs |
kubernetes-amazon-ubuntu-18.04-single |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in alibaba with weave and openebs |
kubernetes-alibaba-ubuntu-18.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in vmware with weave and openebs |
kubernetes-vmware-ubuntu-18.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in vmware with weave and openebs |
kubernetes-vmware-ubuntu-18.04-single |
Kubernetes 1.17 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in fusion with weave and openebs |
kubernetes-1.17-fusion-ubuntu-18.04-single |
Kubernetes 1.16 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in fusion with weave and openebs |
kubernetes-1.16-fusion-ubuntu-18.04-single |
Kubernetes 1.15 Cluster on Ubuntu 18.04, Weave, OpenEBS |
This will provision a single kubernetes master in fusion with weave and openebs |
kubernetes-1.15-fusion-ubuntu-18.04-single |
External Kubernetes 1.17 Cluster |
This will allow access to an external kubernetes cluster |
kubernetes-external-1.17 |
External Kubernetes 1.16 Cluster |
This will allow access to an external kubernetes cluster |
kubernetes-external-1.16 |
External Kubernetes 1.15 Cluster |
This will allow access to an external kubernetes cluster |
kubernetes-external-1.15 |
External Kubernetes 1.14 Cluster |
This will allow access to an external kubernetes cluster |
kubernetes-external-1.14 |
Morpheus Kubernetes Manual Cluster |
This will create a kubernetes manual (self-managed) cluster |
morpheus-kubernetes-manual-cluster |
Kubernetes 1.14 HA Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in bluemix with weave and openebs |
kubernetes-bluemix-ubuntu-16.04-cluster-weave-openebs |
Kubernetes 1.14 Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in bluemix with weave and openebs |
kubernetes-bluemix-ubuntu-16.04-single |
Kubernetes 1.17 HA Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in vcd with weave and openebs |
kubernetes-vcd-ubuntu-16.04-cluster-weave-openebs |
Kubernetes 1.17 Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in vcd with weave and openebs |
kubernetes-vcd-ubuntu-16.04-single |
Kubernetes 1.14 HA Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in softlayer with weave and openebs |
kubernetes-softlayer-ubuntu-16.04-cluster-weave-openebs |
Kubernetes 1.14 Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in softlayer with weave and openebs |
kubernetes-softlayer-ubuntu-16.04-single |
Kubernetes Cluster 1.14 on Ubuntu 16.04, Weave, OpenEBS |
This will provision a kubernetes cluster with weave and openebs |
kubernetes-morpheus-ubuntu-16.04-cluster-weave-openebs |
Kubernetes 1.14 on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master with weave and openebs |
kubernetes-morpheus-ubuntu-16.04-single |
Kubernetes 1.14 HA Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in fusion with weave and openebs |
kubernetes-fusion-ubuntu-16.04-cluster-weave-openebs |
Kubernetes 1.14 Cluster on Ubuntu 16.04, Weave, OpenEBS |
This will provision a single kubernetes master in fusion with weave and openebs |
kubernetes-fusion-ubuntu-16.04-single |
To create a new Kubernetes Cluster:
Navigate to
Infrastructure > Clusters
Select + ADD CLUSTER
Select
Kubernetes Cluster
Select a Group for the Cluster
Select NEXT
Populate the following:
- CLOUD
Select target Cloud
- CLUSTER NAME
Name for the Kubernetes Cluster
- RESOURCE NAME
Name for Kubernetes Cluster resources
- DESCRIPTION
Description of the Cluster
- VISIBILITY
- Public
Available to all Tenants
- Private
Available to Master Tenant
- LABELS
Internal label(s)
Select NEXT
Populate the following:
Note
VMware sample fields provided. Actual options depend on Target Cloud
- LAYOUT
Select from available layouts. System provided layouts include Single Master and Cluster Layouts.
- PLAN
Select plan for Kubernetes Master
- VOLUMES
Configure volumes for Kubernetes Master
- NETWORKS
Select the network for Kubernetes Master & Worker VM’s
- CUSTOM CONFIG
Add custom Kubernetes annotations and config hash
- CLUSTER HOSTNAME
Cluster address Hostname (cluster layouts only)
- POD CIDR
POD network range in CIDR format ie 192.168.0.0/24 (cluster layouts only)
- WORKER PLAN
Plan for Worker Nodes (cluster layouts only)
- NUMBER OF WORKERS
Specify the number of workers to provision
- LOAD BALANCER
Select an available Load Balancer (cluster layouts only) }
- User Config
- CREATE YOUR USER
Select to create your user on provisioned hosts (requires Linux user config in Morpheus User Profile)
- USER GROUP
Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in Morpheus User Profile for all members of User Group)
- Advanced Options
- DOMAIN
Specify Domain override for DNS records
- HOSTNAME
Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
Select NEXT
Select optional Workflow to execute
Select NEXT
Review and select COMPLETE
The Master Node(s) will provision first.
- Upon successful completion of VM provision, Kubernetes scripts will be executed to install and configure Kubernetes on the Masters.
Note
Access to the sites listed in the `Requirements`_ section is required from Master and Worker nodes over 443
After Master or Masters are successfully provisioned and Kubernetes is successfully installed and configured, the Worker Nodes will provision in parallel.
- Provision status can be viewed:
From the Status next to the Cluster in
Infrastructure -> Clusters
Status bar with eta and current step available on Cluster detail page, accessible by selecting the Cluster name from
Infrastructure -> Clusters
All process status and history is available - From the Cluster detail page History tab, accessible by selecting the Cluster name from
Infrastructure -> Clusters
and the History tab - From Operations - Activity - History - Individual process output available by clicking i on target process
Once all Master and Worker Nodes are successfully provisioned and Kubernetes is installed and configured, the Cluster status will turn green.
Important
Cluster provisioning requires successful creation of VMs, Agent Installation, and execution of Kubernetes workflows. Consult process output from
``Infrastructure -> Clusters - Details
and morpheus-ui current logs atAdministration - Health - Morpheus Logs
for information on failed Clusters.
Intra-Kubernetes Cluster Port Requirements¶
The table below includes port requirements for the machines within the cluster (not for the Morpheus appliance itself). Check that the following ports are open on Control-plane and Worker nodes:
Protocol |
Direction |
Port Range |
Purpose |
Used By |
---|---|---|---|---|
TCP |
Inbound |
6443 |
Kubernetes API Server |
All |
TCP |
Inbound |
6783 |
Weaveworks |
|
TCP |
Inbound |
2379-2380 |
etcd server client API |
kube-apiserver, etcd |
TCP |
Inbound |
10250 |
kubelet API |
Self, Control plane |
TCP |
Inbound |
10251 |
kube-scheduler |
Self |
TCP |
Inbound |
10252 |
kube-controller-manager |
Self |
Protocol |
Direction |
Port Range |
Purpose |
Used By |
---|---|---|---|---|
TCP |
Inbound |
10250 |
kubelet API |
Self, Control plane |
TCP |
Inbound |
30000-32767 |
NodePort Services |
All |
Adding Worker Nodes¶
Navigate to
Infrastructure - Clusters
Select
v MORE
for the target clusterSelect
ADD (type) Kubernetes Worker
- NAME
Name of the Worker Node. Auto=populated with
${cluster.resourceName}-worker-${seq}
- DESCRIPTION
Description of the Worker Node, displayed in Worker tab on Cluster Detail pages, and on Worker Host Detail page
- CLOUD
Target Cloud for the Worker Node.
Select NEXT
Populate the following:
Note
VMware sample fields provided. Actual options depend on Target Cloud
- SERVICE PLAN
Service Plan for the new Worker Node
- NETWORK
Configure network options for the Worker node.
- HOST
If Host selection is enabled, optionally specify target host for new Worker node
- FOLDER
- Optionally specify target folder for new Worker node
- Advanced Options
- DOMAIN
Specify Domain override for DNS records
- HOSTNAME
Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
Select NEXT
Select optional Workflow to execute
Select NEXT
Review and select COMPLETE
Note
Ensure there is a default StorageClass available when using a Morpheus Kubernetes cluster with OpenEBS so that Kubernetes specs or HELM templates that use a default StorageClass for Persistent Volume Claims can be utilised.
Kubernetes Cluster Detail Pages¶
Cluster status check results icon
Name of the Cluster
Last sync date, time and duration
- Edit, Delete and Actions buttons
- Actions
- Refresh
Sync the Cluster Status
- Permissions
View and edit Cluster Group, Tenant and Service Plan Access
- View API Token
Displays API Token for Cluster
- View Kube Config
Displays Cluster Configuration
Costs this month (to date, when
Show Costing
is enabled)Cluster resource utilization stats
Counts for current Masters, Workers, Containers, Services, Jobs and Discovered Containers in the Cluster

Kubernetes Cluster summary tab contains:
More Cluster metadata including Name, Type, Created By, Worker CPU, Worker Memory (used/max), Worker Storage (used/max), Enabled: Yes/No, and Description.
Memory chart with total Cluster Free and Used Memory over last 24 hours
Storage chart with total Cluster Reserved and Used Storage over last 24 hours
CPU chart with total Cluster CPU Utilization over last 24 hours
IOPS Chart with total Cluster IOPS over last 24 hours
IOPS Chart with total Cluster Network utilization over last 24 hours






Docker Clusters¶
Provisions a new Docker Cluster managed by Morpheus.
To create a new Docker Cluster:
Navigate to
Infrastructure > Clusters
Select + ADD CLUSTER
Select
Docker Cluster
Populate the following:
- CLOUD
Select target Cloud
- CLUSTER NAME
Name for the Docker Cluster
- RESOURCE NAME
Name for Docker Cluster resources
- DESCRIPTION
Description of the Cluster
- VISIBILITY
- Public
Available to all Tenants
- Private
Available to Master Tenant
- LABELS
Internal label(s)
Select NEXT
Populate the following (options depend on Cloud Selection and will vary):
- LAYOUT
Select from available layouts.
- PLAN
Select plan for Docker Host
- VOLUMES
Configure volumes for Docker Host
- NETWORKS
Select the network for Docker Master & Worker VM’s
- NUMBER OF HOSTS
Specify the number of hosts to be created
- User Config
- CREATE YOUR USER
Select to create your user on provisioned hosts (requires Linux user config in Morpheus User Profile)
- USER GROUP
Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in Morpheus User Profile for all members of User Group)
- Advanced Options
- DOMAIN
Specify Domain for DNS records
- HOSTNAME
Set hostname (defaults to Instance name)
Select NEXT
Select optional Workflow to execute
Select NEXT
Review and select COMPLETE
EKS Clusters¶
Provisions a new Elastic Kubernetes Service (EKS) Cluster in target AWS Cloud.
Note
EKS Cluster provisioning is different than creating a Kubernetes Cluster type in AWS EC2, which creates EC2 instances and configures Kubernetes, outside of EKS.
Create an EKS Cluster¶
Navigate to
Infrastructure - Clusters
Select + ADD CLUSTER
Select
EKS Cluster
Populate the following:
- LAYOUT
Select server layout for EKS Cluster (Kubernetes 1.13 EKS provided)
- PUBLIC IP
- Subnet Default
Use AWS configured Subnet setting for Public IP assignment
- Assigned EIP
Assigned Elastic IP to Controller and Worker Nodes. Requires available EIP’s
- CONTROLLER ROLE
Select Role for EKS Controller from synced role list
- CONTROLLER SUBNET
Select subnet placement for EKS Controller
- CONTROLLER SECURITY GROUP
Select Security Group assignment for EKS Controller
- WORKER SUBNET
Select Subnet placement for Worker Nodes
- WORKER SECURITY GROUP
Select Security Group assignment for Worker Nodes
- WORKER PLAN
Select Service Plan (EC2 Instance Type) for Worker Nodes
- User Config
- CREATE YOUR USER
Select to create your user on provisioned hosts (requires Linux user config in Morpheus User Profile)
- USER GROUP
Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in Morpheus User Profile for all members of User Group)
- Advanced Options
- DOMAIN
Specify Domain for DNS records
- HOSTNAME
Set hostname (defaults to Instance name)
Select NEXT
Select optional Workflow to execute
Select NEXT
Review and select COMPLETE