AWS GPU: Create a Managed Cluster Using the DKP CLI
In previous steps, you created a new Management cluster, which is self-managed. When you use these steps to create new Managed clusters, they will become Attached clusters under your Management Cluster.
When creating Managed clusters, you do not need to create and move CAPI objects, or install the Kommander component. Those tasks are only done on Management clusters!
Choose a Workspace for the New Cluster
If you have an existing Workspace name, run this command to find the name:
⚠️ NOTE: If you need to create a new Workspace, follow the instructions to Create a Workspace.CODEkubectl get workspace -A
When you have the Workspace name, set the
WORKSPACE_NAMESPACE
environment variable:CODEexport WORKSPACE_NAMESPACE=<workspace_namespace>
Name Your Cluster
Follow these steps:
Give your cluster a unique name suitable for your environment.
In AWS it is critical that the name is unique, as no two clusters in the same AWS account can have the same name.
Set the environment variable:
CODEexport CLUSTER_NAME=<aws-additional>
The cluster name may only contain the following characters: a-z
, 0-9
, .
, and -
. Cluster creation will fail if the name has capital letters. See Kubernetes for more naming information.
3. Execute this command to create your Kubernetes cluster using any relevant flags but note that the --self-managed
is absent so that this cluster can be attached to your previously created Management Cluster.
Execute this command to create a cluster with a GPU AMI:
CODEdkp create cluster aws \ --cluster-name=${CLUSTER_NAME} \ --with-aws-bootstrap-credentials=true \ --namespace=${WORKSPACE_NAMESPACE}
If your environment uses HTTP/HTTPS proxies, you must include the flags
--http-proxy
,--https-proxy
, and--no-proxy
and their related values in this command for it to be successful. More information is available in Configuring an HTTP/HTTPS Proxy.Create the node pool after cluster creation:
CODEdkp create nodepool aws -c ${CLUSTER_NAME} \ --instance-type p2.xlarge \ --ami-id=${AMI_ID_FROM_KIB} \ --replicas=1 ${NODEPOOL_NAME} \ --kubeconfig=${CLUSTER_NAME}.conf
Manually Attach a DKP CLI Cluster to the Management Cluster
Find out the
name
of the createdCluster
, so you can reference it later:CODEkubectl -n <workspace_namespace> get clusters
Attach the cluster by creating a
KommanderCluster
:CODEcat << EOF | kubectl apply -f - apiVersion: kommander.mesosphere.io/v1beta1 kind: KommanderCluster metadata: name: <cluster_name> namespace: <workspace_namespace> spec: kubeconfigRef: name: <cluster_name>-kubeconfig clusterRef: capiCluster: name: <cluster_name> EOF