Presenting our journey towards production with Kubernetes and AWS

1. Kubernetes at immmr
Our journey

2. About me
2
▪ ops, infrastructure and security lead at
immmr GmbH
▪ background in software architecture
(SOA), building private cloud
infrastructure, infrastructure as code
▪ strong interest in distributed systems
▪ father of two
▪ esports fan

3. Whether you are sitting at your
computer at work. Or sitting in
another country. Or even if your
phone is off, immmr makes it so
that your mobile world is always
accessible.
About immmr
3
Access your calls, messages, and
contacts from any device. Even if
it’s not your own. Desktop. Tablet.
Home. Or away. Just login.

4. ▪ May 2015 in Silicon Valley
▪ initial idea to use it for Telco requirements of distributed (edge) container clusters
▪ focus on networking, alpha user of project calico <3
▪ Kubernetes WS from Google
Kubernetes first contact
4

5. ▪ joined project as ops lead
▪ ongoing project "microservice-based"
▪ microservices? Yes every service even has its own database, isn't that cool?
▪ Uh, and how do we scale?
From development to production
5

6. ▪ almost, lets go down to 2 databases please --> CouchDB and Postgres
▪ Scaling for free (almost)
▪ service discovery via DNS
▪ many useful features: canary deployment, healing, secrets, configmaps
Kubernetes to the rescue
6

7. ▪ client driven updates: resolved,
deployments 4tw :)
▪ (external) load balancing on AWS - using
terraform automated ELBs; ingress in the
future
▪ persistence layer: currently to afraid to
run our "normal" databases in cluster
▪ transforming configs from chef to
kubernetes
The gaps
7

8. ▪ auto-scaling
▪ namespaces: cluster-in-cluster
▪ dynamic storage allocation via EBS
▪ automated ELB setup or ingress
The future
8

9. ▪ jannis@immmr.com
▪ Twitter: @jannis_r
Questions
9