CNA weekly #003

Wow – I had no idea this newsletter idea would become so popular so soon. Thanks everyone for signing up! I want to keep this as interesting as possible. Feel free to forward this newsletter to your friends and colleagues. And please send feedback or ideas anytime – I am always open for suggestions (e.g. via Twitter @bbrundert).

Pivotal Container Service
In case you missed it last week: Pivotal Container Service is now generally available. Check out these blogposts that capture some of the highlights:

Here is the download link for Pivotal Container Service (PKS) on Pivotal Network. You need to create an account to get to the download bits. Documentation can be found here

VMware Cloud Native Applications and Platform News

 
Kubernetes / Container Ecosystem

“All-things Cloud-Native” Newsletter

Last week I started a small experiment that I have been thinking about for some time now: a newsletter about all-things “Cloud-Native”. I have been using Twitter and RSS/feedly for quite some time now to keep up with my favorite areas of technology. But it’s tough – there is just too much going on. Some people asked me how I keep up with all these fast-moving topics and news and also stay engaged e.g. on Twitter. In essence, I made this part of my daily routine and I keep improving that practice each day. I also found inspiration on some other newsletters that I started to find useful for myself (e.g. cron.weekly or devops weekly) – in a world of literally 1000s new updates per day, a solid newsletter can be quite valuable.

Over the past years I already captured content from various channels that I found useful and shared that in a structured manner with my customers. But I feel there might be value in this – now laser focused on Cloud-Native – even for people outside of my direct network. So I decided to formalize it even further and offer my very personal summary of highlights from the week in a newsletter. From a tool perspective I picked tinyletter because it feels like there isn’t much overhead for the sender, it has a clean interface and a pretty straight-forward archive option.  



CNA weekly #002

After some issues with sending out #001 of this newsletter, I’ll try again with some different settings on tinyletter. Sorry for yet another email tonight – I promise it’ll be the last one for today!

News:

CNA weekly #001

Welcome to this little Cloud Native newsletter! 

The world of Cloud Native Applications and Platforms is moving very fast – the goal of this newsletter is to capture some highlights from the previous week: blogposts, videos, tweets or other valuable links that I came across. Feel free to forward this newsletter to your friends and colleagues. I promise to keep it interesting and I am always open for suggestions (e.g. via Twitter @bbrundert).
 

Pivotal Container Service

vSphere Integrated Containers

VMware Cloud Native Applications and Platform News

Kubernetes / Container Ecosystem

Running Kubernetes on VMware – a brief overview about the options

After I shared a brief overview about running Containers on vSphere, I’d like to go a little further this time and share the VMware intergration points with Kubernetes. As you are probably aware of, VMware has just released it’s own Kubernetes distribution called “Pivotal Container Service” which became generally available on Februrary 12, 2018. While this is VMware’s and Pivotal’s recommended and preferred way to run Kubernetes in an Enterprise environment, there are several options to either consume any other Kubernetes distribution or build Kubernetes solely from opensource. No matter what path you choose, VMware has a variety of solutions to offer.

 

Compute / Cloud Provider

Network & Security

Storage

Monitoring

Container Management

  • Project Harbor: An Enterprise-class Container Registry Server based on Docker Distribution, embedded in Pivotal Container Service and vSphere Integrated Containers
  • vRealize Automation: governance and self-service to request K8s clusters, nodes and e.g. namespaces; custom integration/blueprints required

3rd Party Documentation