In this blog post, I will share my experience, hopefully step by step on installing PKS 1.0 on NSX-T 2.1.
You can refer to my previous blog posts on how to install NSX-T 2.1.
PKS 1.0 has gone GA on the 8 Feb 2018! Its kinda weird that there is not much announcement on the web.
I am super excited about PKS as it has native integration with NSX-T!
- Create, resize, delete, list, and show clusters through the PKS CLI
- Native support for NSX-T and Flannel
- Easily obtain kubeconfigs to use each cluster
- Use kubectl to view the Kubernetes dashboard
- Define plans that pre-configure VM size, authentication, default number of workers, and addons when creating Kubernetes clusters
- User/Admin configurations for access to PKS API
- Centralized logging through syslog
In the following blog post, I’m going to start blogging about my experience on installing PKS 1.0 on my existing NSX-T 2.1 setup. I think its going to be fun.
From VMware PKS architecture, slide from VMworld 2017 US, you can see there is NSX to provide the network & security services for BOSH. To be more precise, this is going to be NSX-T. In the following few posts, I will cover setting up the vSphere Lab and prepare the hosts for NSX-T, and be ready for PKS.
Introducing NSX-T 2.1 with Pivotal Integration
As you might have guess it by now, the version of NSX-T I will be using the lab will be 2.1 which supports PCF2.0 and PKS, specially I want to understand the CNI plugin.
Stay tune. In the next few posts, I will cover the installation of vSphere, NSX-T, PCF and PKS.
Pivotal Container Service (PKS) was announced in VMworld 2017 US. Its not GA yet but through the VMworld CNA sessions, I learnt that its going to use BOSH to spin up Kubernetes cluster, thus the name KUBO – Kubernetes on BOSH. Through my googling, I saw my fellow colleague Simon from Ireland had the same thinking and did a fantastic job in detailing in the installation steps required to get KUBO up and running.
My First KUBO Deployment Screenshots
Below you can see the kubernetes cluster spun up by BOSH. I had to scale down some of the nodes due to the limited amount of Memory and Storage resources I had.
Below show the vSphere resources. Almost consuming all resources on my 64GB RAM, 1TB Storage Host.
The screenshot below shows the amount of storage those k8s nodes consume.
This is the worker node. You can identify from the Custom Attributes. 121.2GB Storage Used. Ouch!
Thats about it. Next I will be setting up NSX-T for PKS. Follow the very good guide by Simon Guyennet – https://blog.inkubate.io/deploy-kubernetes-on-vsphere-with-kubo/