Past Meetup

Vienna Kubernetes/Cloud-Native Meetup

This Meetup is past

65 people went


Hi Kubernauts,

our first Kubernetes/Cloud-Native Meetup in Vienna will take place on Wednesday, March 13, 201 @Stockwerk Coworking GmbH.

Since there are already many different groups on the subject of Kubernetes and Cloud Native in Vienna, and none has really become established, we would like to create a new platform where the community can exchange ideas and learn from each other.

If you would like to present or host feel free to reach out to me via mail ([masked]) or submit your talk via

6:30 - Admission
7:00 - Christian Kurze
7:30 - Tobias Schneck
8:00 - Beer, Pizza & Networking


Christian Kurze, mongoDB

Cloud-Native MongoDB: DBaaS on AWS, GCP and Azure via MongoDB Atlas or Flexible Deployment in MongoDB Kubernetes Operator

Everyone talks about cloud-native - DevOps should have an easy life with less manual tasks and automated failure recovery; Developers should have an easy life to have production-ready environments with a single click or command. MongoDB promises to run the same everywhere: local laptop, datacenter, mainframe, cloud as well as hybrid scenarios. This demo session will introduce the cloud capabilities of MongoDB: Atlas offers database as a service on the three major cloud providers (AWS, Azure, GCP), the Kubernetes Operator natively integrates deployments into K8s clusters.


Tobias Schneck, Loodse

ClusterAPI Overview - Managing multi-cloud Kubernetes Clusters

Thanks to tools like kubeadm, Terraform or Ansible setting up a Kubernetes cluster on a dedicated environment is getting reachable, but what’s about setting up a bunch of cluster in multiple clouds in automatic way? This is still a challenge. Also if you want to do same in your own datacenter. In this talk we will take a look to the approach to orchestrate and manage a whole set of k8s cluster by the Cluster API project of kubernetes (a sub-project of sig-cluster-lifecycle). The main idea behind it is to use the Kubernetes API itself to manage multiple clusters with there master and worker nodes in same way you would manage your PODs - define the needed resources and the responsible controller will take care for providing it.

After an overview about the concepts of cluster API, I will show what’s needed to implement a cluster API conform machine class/deployment. There I will see that adding your own provider isn’t that hard as you may aspect. At the end of the day it just requires a simple interface to implement. The corresponding Kubermatic machine-controller we implemented at Loodse are available as open source, so its possible to play around with it. A live demo will show how easy it is to spin up and maintain multiple Kubernetes cluster at different public and on-premise cloud providers over one managing cluster. A final wrap up will summarize the current state of the Cluster API project and the advantages of managing clusters with CRDs and Controllers instead of stateful scripts.