PKS in Action

By Al
Now it is a good time to develop an interest in container technology. Nowadays when we think about containers, Docker comes right to mind. Containers is not a new technology. It has been available in Linux in various shapes and forms for a number of years. The real merit of Docker is how super easy it made to package and distribute software along with its dependencies and hence its popularity. However many people started to wonder if it could be taken one step further.

I like to compare Docker with VMware Workstation. It is great to create and run multiple virtual machines in my laptop but if I want those VMs to run a mission critical workload relying on a single server is not a great idea. For production I would like to see the capability to withstand hardware failures or at least to recover from them quickly. And that's why VMware has products like ESX and vCentre.

We need the similar capabilities in the container world, in other words we need to manage the orchestration of containers across a cluster of systems. This is provided by what we call CO's (Container Orchestrators). For a while that space has seen 3 main competitors: Mesosphere, Kubernetes and Docker Swarm, and for a long time it was hard to discern who was going to be the "VHS" and who was going to be the "Beta". It seemed counter-intuitive to bet against Docker's own orchestrator called Swarm, but the reality is that one clear winner is starting to emerge and that is no other than Kubernetes, which was created by Google

So it is no surprise that, now that the dust is settling, we start to see solutions like PKS. This has been jointly developed by Pivotal, Google and VMware. The thing with Kubernetes is that it does a good job at orchestrating the containers themselves but it doesn't solve the problem of operating the VM's that underpin Kubernetes itself. That's where Pivotal expertise comes into play. Cloud Foundry (and now PKS as well) leverages BOSH to make day 1 (deploy) and day 2 (upgrade, HA and scale) operations a breeze.


So what is PKS? A turnkey solution to provision, operate and manage enterprise-grade Kubernetes clusters. Besides BOSH and its proven benefits PKS provides:

  • NSX-T from VMware. Kubernetes is a bit limited in terms on network capabilities. NSX-T on the other hand provides micro-segmentation and a phenomenal range of other network capabilities
  • Harbor from VMWare. It is an enterprise-grade container registry that prevents you from storing or deploying containers images if they contain security vulnerabilities.
  • GCP Broker. It allows apps running in PKS to transparently access all the great offerings from Google Cloud API's
Anyway, that's enough talking for today. You came here to watch PKS in action. The video below shows how to deploy Pivotal Ops Manager and PKS. After you will marvel at how easy it is to spin up a Kubernetes cluster. The video has been produced by my colleague and Pied Piper partner-in-crime Theo Crithary. Enjoy!!


Comments

Post a Comment

Popular posts from this blog

Sending PowerStore alerts via SNMP

By Al
Image
In this previous article we discussed how to leverage PowerStore's powerful API to collect audit logs and send them to a Syslog server . We used Logstash to do that because of its extensive list of plugins Sometimes I come across organizations that still have a requirement to send storage array Alerts to SNMP. As in the Syslog case, ultimately most modern monitoring tools today support collecting information via REST API because that's the way the application world is going, i.e. the cloud native way ... it would be fun to see Prometheus monitoring Kubernetes via SNMP :) However there is still some requirement out there for SNMP traps, so we will explore how to do it. For simplicity we will use the same toolset that we used in the previous article. I encourage you to revisit quickly the article as we did an extensive introduction to Logstash, with practical examples as well as a description of the logs available in PowerStore. I won't cover those aspects in this article I
Read more

Electronic Nose - eNose

By Al
Image
In the previous article I provided details on VeeFarm which was one of the best projects we saw in ANZ Pied Piper 2019 edition and one of the best projects in the history of the program. The program inspired me and others to work together to showcase a great idea and the Pied Piper program itself during our presales conference. An idea I suggested to enhance VeeFarm was an electronic nose that could be used to detect the optimal ripening of the produce to advise the owner that it is the right time to pick it up the produce. This is an idea I had in the backburner for a while but never found the time to work on. Vee gave me the perfect excuse. The electronic nose, or eNose for short, is a custom PCB that hosts a range of gas sensors. For the proof of concept, I used the cheap MQ sensors. These are designed mostly for hobbyists and makers and they barely cost $1 per sensor. As one could expect, tweaking and calibrating these sensors it is even harder than the most expensive counter
Read more

Use Vagrant to deploy to AWS

By Al
Image
In the Pied Piper program we run through a Vagrant tutorial as we found it a great tool to help set up other labs. We are not going to cover Vagrant in detail in this blog as there are plenty of good examples out there. If you are interested in the exercises we did you can visit the repository: https://github.com/cermegno/vagrant-lesson However, something I felt is not sufficiently document and would make a good candidate for a post is how to use Vagrant to deploy to AWS and particularly from Windows. I found a couple of posts that provided good detail but none of them prevented me from running into Windows specific issues. If you are running it from Linux, this article will still help you as I will point out the differences anyway. Install prerequisites Firstly, as the Vagrant documentation states, "providers" other than VirtualBox require a plug in. This is how you install the AWS provider: vagrant plugin install vagrant-aws Deploying to AWS EC2 generally mea
Read more