As you can see from my recent tweets, I have been spending some time with Kubernetes Cluster API (CAPI) and specifically Cluster API Provider vSphere (CAPV) and deploying upstream Kubernetes (K8s) running on VMware Cloud on AWS 🙂
Looks like this week’s theme for me will be:
🔸CAPI (K8s Cluster API)
🔹CAPV (K8s Cluster API Provider for vSphere)
🔸KIND (K8s in Docker)
🔹TKG (@VMwareTanzu K8s Grid)Already learned quite a bit in last 24hrs, huge thanks to @vmmannimal & @KendrickColeman for answering quest.
— William Lam (@lamw) March 2, 2020
Just deployed my first @VMwareTanzu K8s Grid Management and Workload Cluster (12-Node), using #CAPI via #CAPV all running on #VMWonAWS 🥳 pic.twitter.com/TI9AEbkBew
— William Lam (@lamw) March 2, 2020
After successfully deploying my first K8S Workload Cluster, I knew the first k8s application that I had to deploy on my shiny new K8s Cluster was Massimo Re Ferre' and Andrea Siviero famous "Yelb" application which I had demonstrated several years ago running on VMware PKS. In fact, I had even deployed it recently (late last year) in one of my Project Pacific cluster without any issue, so I was surprised when I ran into some challenges as you can see from the title of the blog post.