Node pools are a logical construct used with TMC-provisioned clusters. You can define a node pool while provisioning a cluster or after the cluster has already been created. A node pool will allow you to segregate your worker nodes based on location (primarly), size, or on some other deciding factor. This functionality is only available for […]
Inspections in TMC are using Sonobuoy within the cluster to do their work. You could use Sonobuoy directly and bypass TMC but it would take a little bit of configuration that TMC handles for you…it’s really not much if you’ve got access to TMC, why bother with it? You also wouldn’t get the great UI experience that
I hadn’t used TMC in a few months so decided to revisit the process for creating a TKG cluster on AWS. Just like months ago, I’m still impressed at how all of this works and you can end up with an OCI conformant Kubernetes cluster built with ClusterAPI on AWS. Note: These instructions assume you
I had been so focused on TKG on vSphere lately that I had been overlooking the fact that we’ve automated the process for standing up a cluster on AWS as well. While it’s far easier to do this via the TKG UI, I wanted to take a stab at it entirely from the command line.