Closed joshrosso closed 3 years ago
Using the below steps, I created management and worker clusters.
The management cluster took 11 minutes 14 seconds to spin up. The worker cluster took 7 minutes 53 seconds to spin up.
So, roughly 19 minutes to get a usable cluster.
tar xvf tkg-linux-amd64-v1.2.1-vmware.1.tar
sudo cp -p tkg/tkg-linux-amd64-v1.2.1+vmware.1 /usr/local/bin/tkg
export AWS_ACCESS_KEY_ID=ABCDEFGHIJKLMNOPQRST
export AWS_SECRET_ACCESS_KEY=ABC12+ABCDEFGHIJKLMNOPQRSTUVWXYZ01234567
export AWS_REGION=us-east-1
export AWS_SSH_KEY_NAME=default
export MANAGEMENT_CLUSTERNAME=manager
tkg init --infrastructure=aws --name=${MANAGEMENT_CLUSTERNAME} --plan=dev
export WORKER_CLUSTERNAME=worker
tkg create cluster ${WORKER_CLUSTERNAME} --plan=dev
tkg get credentials ${WORKER_CLUSTERNAME}
kubectl apply -f ...
tkg delete cluster ${WORKER_CLUSTERNAME}
# Have to wait for the worker to be deleted before you can delete the management cluster
# This takes awhile as well
tkg delete management-cluster ${MANAGEMENT_CLUSTERNAME}
Just to get this captured somewhere, here's some data on deployment to a vSphere cluster. Local single node lab environment.
Hypervisor: VMware ESXi, 7.0.1, 17325551
Model: System Product Name
Processor Type: AMD Ryzen 7 1700X Eight-Core Processor
Logical Processors: 16
NICs: 2
Cloning to-from the same 1TB drive.
Time not including setup of tkg CLI.
Management cluster deployment: ~11 minutes Workload cluster deployment: 5:37
We'd like to be able to get a human up and running with a cluster that can run workloads in 10 minutes or less.
Using the v0.1.0 release, essentially tkg 1.2.1, time a cluster bootstrapping in AWS to get our current metric.
Start timing after downloading
tkg
and stop timing after the guest cluster nodes reportReady
.