We are excited to announce another interesting and expiring meetup in Aarhus. This time we focus on some of the options you have on Google Cloud. If you are interested in learning more about Google Kubernetes Engine, Google Cloud Run, or just what the f*ck Anthos is, then this meetup is definitely for you! Besides these great talks, another very sought topic is on the agenda, namely: real-world experience with a service mesh implementation, Istio.
17:00: Welcome by Cloud Native Aarhus
17:05: Welcome by today's host; Trifork
17:15: How Google Kubernetes Engine is different and what the f*ck is Anthos, Alejandro Montenegro
17:45: Break with food
18:15: How Cloud Run is the final destination in my Cloud Native journey, Kevin Simper
18:45: Real world Istio - War stories and Gotchas, Lasse Højgaard & Frederik Mogensen - Trifork
19:15: Networking and discussion
20:00: Thank you and good night
TALK 1: How Google Kubernetes Engine is different and what the f*ck is Anthos
Speaker: Alejandro Montenegro
A look into the details on how Google's managed Kubernetes service (GKE) takes advantage of Google Cloud to provide a reliable service for running mission critical workloads. Then a look into how Google sees the future of Kubernetes and the born of Anthos.
TALK 2: How Cloud Run is the final destination in my Cloud Native journey
Speaker: Kevin Simper - Google Cloud Developer Group
In this talk I will look at my cloud native journey, how I came here and why I think Cloud Run is the final destination. What did we solve along the way and how I combine my tools to do the best job I can.
But do we still miss some things and what is the downsides? Let us talk about that.
TALK 3: Real world Istio - War stories and Gotchas
Speaker: Lasse Højgaard & Frederik Mogensen - Trifork
In a public health care project requirements for security and data protection are very rigid - can Istio help us solve these requirements? And at what cost?
We will talk about using Istio for running a multi-tenant setup, allowing the different tenants to talk to the core services on the platform, but not disrupting each other.
Enforcing security between services using the service mesh, by demanding JWT tokens on all requests, adding mutual encryption, locking down egress traffic, disallowing inter-namespace traffic, etc.
We’ll share our experiences running Istio, war stories, bugs found, and failures.