Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Tobias Schmidt
KubeCon 2015 - San Francisco
Moving to Kubernetes
Tales from SoundCloud
http://prometheus.io
Why containers?
What is Bazooka?
What have we learned?
Why Kubernetes?
What’s next?
Why did we build a container
runtime environment?
slow scaling
fragile deploys
inconsistent state
cumbersome new app setup
What is Bazooka?
$ bazooka init
$ bazooka push
$ bazooka scale ...
$ bazooka ps
...
12-Factor applications
immutable revisions
declarative deploys
LXC
agent on each node
consensus store
CLI
What are the strengths
of Bazooka?
independent teams
quick
deploys / rollback / scaling
orchestration is not
in the critical path
What have we learned?
containers are the only way
Golang is a great fit
monitoring dynamically
deployed services is complex
choose the right data store
use a common
integration service
resource isolation is important
automate everything
Why moving on?
Bazooka doesn’t fit anymore
problem is too big for us alone
Docker et al.
Why Kubernetes?
simple domain objects
(container, pod, service, rc)
powerful networking
(security, auditing, performance)
pod scheduling
label system
(grouping, discoverability, resource constraints)
community + support
extends Bazooka concepts
What’s next?
cluster runs on bare-metal
continuous integration pipeline
Prometheus monitoring
integration
logging integration
service discovery integration
THANK YOU
@dagrobie
https://github.com/grobie
Moving to Kubernetes - Tales from SoundCloud
Moving to Kubernetes - Tales from SoundCloud
Upcoming SlideShare
Loading in …5
×

Moving to Kubernetes - Tales from SoundCloud

3,050 views

Published on

KubeCon 2015 talk about SoundCloud's container runtime environment history and a few highlighted reasons to migrate to Kubernetes.

Published in: Software
  • Be the first to comment

Moving to Kubernetes - Tales from SoundCloud

  1. 1. Tobias Schmidt KubeCon 2015 - San Francisco Moving to Kubernetes Tales from SoundCloud
  2. 2. http://prometheus.io
  3. 3. Why containers? What is Bazooka? What have we learned? Why Kubernetes? What’s next?
  4. 4. Why did we build a container runtime environment?
  5. 5. slow scaling
  6. 6. fragile deploys
  7. 7. inconsistent state
  8. 8. cumbersome new app setup
  9. 9. What is Bazooka?
  10. 10. $ bazooka init $ bazooka push $ bazooka scale ... $ bazooka ps ...
  11. 11. 12-Factor applications immutable revisions declarative deploys
  12. 12. LXC agent on each node consensus store CLI
  13. 13. What are the strengths of Bazooka?
  14. 14. independent teams
  15. 15. quick deploys / rollback / scaling
  16. 16. orchestration is not in the critical path
  17. 17. What have we learned?
  18. 18. containers are the only way
  19. 19. Golang is a great fit
  20. 20. monitoring dynamically deployed services is complex
  21. 21. choose the right data store
  22. 22. use a common integration service
  23. 23. resource isolation is important
  24. 24. automate everything
  25. 25. Why moving on?
  26. 26. Bazooka doesn’t fit anymore
  27. 27. problem is too big for us alone
  28. 28. Docker et al.
  29. 29. Why Kubernetes?
  30. 30. simple domain objects (container, pod, service, rc)
  31. 31. powerful networking (security, auditing, performance)
  32. 32. pod scheduling
  33. 33. label system (grouping, discoverability, resource constraints)
  34. 34. community + support
  35. 35. extends Bazooka concepts
  36. 36. What’s next?
  37. 37. cluster runs on bare-metal
  38. 38. continuous integration pipeline
  39. 39. Prometheus monitoring integration
  40. 40. logging integration
  41. 41. service discovery integration
  42. 42. THANK YOU @dagrobie https://github.com/grobie

×