🗂 Link: VMware Adds Containers to Its Cloud Provider Platform

The platform also added an integration with VMware’s container orchestrator, Enterprise PKS, which means cloud providers can offer containers-as-a-service. And at VMworld the vendor will showcase a technology preview of vCloud Director integration with Bitnami Community.

VMware bought Bitnami in May. It provides application packaging targeted at container and Kubernetes environments. The Bitnami Community houses one of the largest catalogs of click-to-deploy applications and development stacks. Combining this with and Enterprise PKS will allow VMware Cloud Providers to “provide a cloud that’s developer ready, and offer both VM-based workloads and container-based workloads from the same platform,” Bhardwaj said

Source: VMware Adds Containers to Its Cloud Provider Platform

Link: VMworld 2018: Pivotal Container Service and the Long Road to NoOps

[Swisscom’s] Massalt polled the audience, asking how many of them had experience with updating their Kubernetes clusters. No one, in a reasonably full ballroom, raised a hand.

“There’s a reason for this: because it’s a painful process,” he said. It’s why Swisscom had already adopted BOSH as an automated deployment tool for replacing old versions and updating the underlying platform, thus taking care of a large chunk of Day-2 operations.
Original source: VMworld 2018: Pivotal Container Service and the Long Road to NoOps

Link: VMworld 2018: VMware Wants to Re-Architect Your Containers for NSX – The New Stack

“The developer shouldn’t have to know how to program NSX, or know what the security isolation boundaries are,” continued Fazzone. “But they should know that their organization has taken steps to unify the networking approach between the containerized applications and the traditional applications running in VMs, and take advantage of that ‘service’ offered by IT to extend the NSX-T support up into their container platform, versus just defaulting to the Layer 2 default that’s available in the open source community — so that their organization can realize that complete connectivity model in a consistent way.”
Original source: VMworld 2018: VMware Wants to Re-Architect Your Containers for NSX – The New Stack

Link: Using VMware’s Harbor with PKS (and Why Kubernetes Needs a Container Registry)

“A container registry is the repository for all your container images. Since your core business applications are packaged into containers (built out of container images), you must protect these images just as you would any other important enterprise IT system. That’s where the image registry comes into play.”
Original source: Using VMware’s Harbor with PKS (and Why Kubernetes Needs a Container Registry)

Link: VMware might just have cracked the container market with NSX

“But perhaps the most significant news was that VMware has started to see customers buy its NSX network virtualization software just to put it to work with the Pivotal Container Service.”
Original source: VMware might just have cracked the container market with NSX

Link: VMware might just have cracked the container market with NSX

“But perhaps the most significant news was that VMware has started to see customers buy its NSX network virtualization software just to put it to work with the Pivotal Container Service.”
Original source: VMware might just have cracked the container market with NSX

Link: PKS: The answer for “everything else” in your data center

“PKS will provide a comfortable environment to run freshly containerized legacy workloads and packaged software in an on-premise model to start, if desired, on top of VMWare vSphere.”
Original source: PKS: The answer for “everything else” in your data center

Stateless apps in one, stateful apps in the other

It happens to be the case that CF — because it’s an app platform and wants to let the user focus on their code — provides a way to convert code in to containers inside the platform without having to start messing around with Dockerfiles and the like. And this functionality even does some cool things for you like keeping your container OS automatically patched so you don’t have to build CI pipelines to monitor your base images and rebuild stuff.

That’s why I love Cloud Foundry’s Application Runtime. Of course, because of these constraints — the constraints that are why I love it — the App Runtime can’t possibly work for complex stateful services: the whole point is for it not to. And that’s why it’s fantastic that there’s now a Container Runtime (which I wish we’d called a Stateful Services Runtime because that’s how I think of it).

Source: CF vs Kube: Is the difference who creates the container?

Bloomberg on kubernetes in Cloud Foundry

On overview of how Bloomberg is looking at the likes of Pivotal Container Services:

“Many Kubernetes distributions are good on day one, when they’re first deployed,” said Andrey Rybka, technical architect in the office of the CTO at Bloomberg, the global finance, media and tech company based in New York. “But what happens on day two, when something fails? Kubernetes doesn’t [automatically] address things like failures at the physical node level.”

And:

The roadmap for Cloud Foundry Container Runtime includes support for stateful applications based on the StatefulSets feature that became available with Kubernetes 1.7 in June. The foundation also plans to integrate the Istio project, founded by IBM, Google and Lyft in May, which helps to manage network communications between microservices

Also, see coverage of the general announcement in TechCrunch, the related press release, and our discussion in this week’s podcast.

Source: Cloud Foundry Container Runtime eases Kubernetes ops