Happy Monday everyone!
Another exciting week has passed and I had several great meetings across the region. And I love my new PKS socks – socks are the new stickers 😉
But lets take a look at some of the content from last week:
William Lam (@lamw) has continued his work on the Getting started with VMware Pivotal Container Service (PKS) blogpost series with a seventh part about the integration with the container registry Harbor (after Overview, PKS Client, NSX-T, Ops Manager and BOSH, PKS Control Plane, Kubernetes Go!)
Speaking of PKS: there will be a PKS roadshow across the US and then coming to cities across Europe very soon. Make sure to sign-up here if you are interested in learning more. I’ll publish additional dates as soon as they are releases.
At the same time, NSX-T and the NSX Container Plugin (NCP) have been released in version 2.1.2. NSX-T now supports Kubernetes 1.10.
Speaking of NSX-T: the team just released a Terraform provider for NSX-T and demonstrates its capabilities in a 20min video focused on Infrastructure as Code with NSX-T.
VMware Distributed Resource Scheduler (DRS) has been embedded in VMware’s core virtualization product for over a decade and VMware customer are leveraging its algorithms to let the infrastructure load-balance itself in a “driverless” fashion. A newly released whitepaper gives some insights into what’s new and what’s current with vSphere 6.5’s implementation of DRS and explains many of the concepts and metrics in more detail.
I somehow missed the release of a great whitepaper titled “Performance of Enterprise Web Applications in Docker Containers on VMware vSphere 6.5“.
Dispatch Framework 0.1.11 has been released as well – “Lots of new stuff including open service broker support for services and language packs to easily expand supported language runtimes.”
An interesting perspective and findings from reality are included in the blogpost called “Another reason why your Docker containers may be slow”. Quoting the article: “It re-iterates on the fact that containerization != virtualization and demonstrates how containerized processes can compete for resources even if all cgroup limits are set to reasonable values, and there’s plenty of computing power available on the host machine.”