Download as PDF, PPTX
![‹#›
@tpryan
# BACKEND
FROM ubuntu:12.04
ADD ./mysql-setup.sh /tmp/mysql-setup.sh
RUN /bin/sh /tmp/mysql-setup.sh
EXPOSE 3306
CMD ["/usr/sbin/mysqld"]](https://image.slidesharecdn.com/terry-containingchaoswithkubernetes-151012084600-lva1-app6891/85/Containing-Chaos-with-Kubernetes-Terrence-Ryan-Google-DevOpsDays-Tel-Aviv-2015-6-320.jpg)
![‹#›
@tpryan
# BACKEND
FROM ubuntu:12.04
ADD ./mysql-setup.sh /tmp/mysql-setup.sh
RUN /bin/sh /tmp/mysql-setup.sh
EXPOSE 3306
CMD ["/usr/sbin/mysqld"]](https://image.slidesharecdn.com/terry-containingchaoswithkubernetes-151012084600-lva1-app6891/85/Containing-Chaos-with-Kubernetes-Terrence-Ryan-Google-DevOpsDays-Tel-Aviv-2015-16-320.jpg)
![‹#›
@tpryan
# BACKEND
FROM ubuntu:12.04
ADD ./mysql-setup.sh /tmp/mysql-setup.sh
RUN /bin/sh /tmp/mysql-setup.sh
EXPOSE 3306
CMD ["/usr/sbin/mysqld"]
# BACKEND
FROM ubuntu:12.04
ADD ./mysql-setup.sh /tmp/mysql-setup.sh
RUN /bin/sh /tmp/mysql-setup.sh
EXPOSE 3306
VOLUME ["/etc/mysql", "/var/lib/mysql"]
CMD ["/usr/sbin/mysqld"]](https://image.slidesharecdn.com/terry-containingchaoswithkubernetes-151012084600-lva1-app6891/85/Containing-Chaos-with-Kubernetes-Terrence-Ryan-Google-DevOpsDays-Tel-Aviv-2015-17-320.jpg)
Uploaded byDevOpsDays Tel Aviv
Containing Chaos with Kubernetes - Terrence Ryan, Google - DevOpsDays Tel Aviv 2015
The document discusses Kubernetes and container orchestration. It begins with an introduction to the problem of managing containers and microservices across multiple machines. It then covers key Kubernetes concepts like pods, controllers, services, labels and selectors. It also demonstrates Kubernetes in action and discusses options for hosting Kubernetes clusters, particularly Google Container Engine which provides a hosted Kubernetes environment.
More Related Content
Similar to Containing Chaos with Kubernetes - Terrence Ryan, Google - DevOpsDays Tel Aviv 2015
More from DevOpsDays Tel Aviv
Containing Chaos with Kubernetes - Terrence Ryan, Google - DevOpsDays Tel Aviv 2015
- 1. ‹#› @tpryan Terrence Ryan Developer Advocate ContainingChaos with Kubernetes
- 2.
- 3.
- 4. ‹#› @tpryan What problem are we trying to solve?
- 5. ‹#› @tpryan # FRONTEND ANDSERVICES FROM nginx-php-fpm COPY nginx.conf /etc/nginx/nginx.conf ADD www /var/www/
- 6. ‹#› @tpryan # BACKEND FROM ubuntu:12.04 ADD./mysql-setup.sh /tmp/mysql-setup.sh RUN /bin/sh /tmp/mysql-setup.sh EXPOSE 3306 CMD ["/usr/sbin/mysqld"]
- 7.
- 8.
- 9.
- 10. ‹#› @tpryan # FRONTEND ANDSERVICES FROM nginx-php-fpm COPY nginx.conf /etc/nginx/nginx.conf ADD www /var/www/
- 11. ‹#› @tpryan # FRONTEND ANDSERVICES FROM nginx-php-fpm COPY nginx.conf /etc/nginx/nginx.conf ADD www /var/www/ # JUST SERVICES FROM nginx-php-fpm COPY nginx.conf /etc/nginx/nginx.conf ADD www /var/www/
- 12. ‹#› @tpryan # FRONTEND ANDSERVICES FROM nginx-php-fpm COPY nginx.conf /etc/nginx/nginx.conf ADD www /var/www/
- 13. ‹#› @tpryan # FRONTEND ANDSERVICES FROM nginx-php-fpm COPY nginx.conf /etc/nginx/nginx.conf ADD www /var/www/ # FRONTEND FROM nginx COPY nginx.conf /etc/nginx/nginx.conf ADD www /var/www/
- 14.
- 15.
- 16. ‹#› @tpryan # BACKEND FROM ubuntu:12.04 ADD./mysql-setup.sh /tmp/mysql-setup.sh RUN /bin/sh /tmp/mysql-setup.sh EXPOSE 3306 CMD ["/usr/sbin/mysqld"]
- 17. ‹#› @tpryan # BACKEND FROM ubuntu:12.04 ADD./mysql-setup.sh /tmp/mysql-setup.sh RUN /bin/sh /tmp/mysql-setup.sh EXPOSE 3306 CMD ["/usr/sbin/mysqld"] # BACKEND FROM ubuntu:12.04 ADD ./mysql-setup.sh /tmp/mysql-setup.sh RUN /bin/sh /tmp/mysql-setup.sh EXPOSE 3306 VOLUME ["/etc/mysql", "/var/lib/mysql"] CMD ["/usr/sbin/mysqld"]
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28. ‹#› @tpryan That’s a lotto manage.
- 29.
- 30.
- 31. ‹#› @tpryan 02 Concepts What isKubernetes?
- 32.
- 33.
- 34.
- 35.
- 36. ‹#› @tpryan Build Script ./create_docker_images.sh ./launch_frontend.sh x3 ./launch_services.sh x 2
- 37. ‹#› @tpryan Build Script ./create_docker_images.sh ./launch_frontend.sh x3 ./launch_services.sh x 2 ./launch_backend.sh x 1
- 38. ‹#› @tpryan Build Script ./create_docker_images.sh ./launch_frontend.sh x3 ./launch_services.sh x 2 ./launch_backend.sh x 1
- 39. ‹#› @tpryan Build Script ./create_docker_images.sh ./launch_frontend.sh x3 ./launch_services.sh x 2 ./launch_backend.sh x 1
- 40. ‹#› @tpryan Build Script ./create_docker_images.sh ./launch_frontend.sh x3 ./launch_services.sh x 2 ./launch_backend.sh x 1
- 41. ‹#› @tpryan Desired State There shouldbe: 3 Frontends 2 Services 1 Backend
- 42. ‹#› @tpryan Desired State There shouldbe: 3 Frontends 2 Services 1 Backend
- 43. ‹#› @tpryan Desired State There shouldbe: 3 Frontends 2 Services 1 Backend
- 44. ‹#› @tpryan Pods • Atomic componentof Kubernetes • Made from one or more containers • It’s okay to have just one container • Share • IP Address • Namespace • Examples • Webserver + CMS • All Web available services • Converting an all in one box
- 45. ‹#› @tpryan Containers • Subatomic particlesof Kubernetes • Dockerfiles just like you are used to.
- 46. ‹#› @tpryan Controllers • Handle turningcurrent state into desired state • Example • Replication Controllers
- 47. ‹#› @tpryan Controllers • Handle turningcurrent state into desired state • Example • Replication Controllers Observe
- 48. ‹#› @tpryan Controllers • Handle turningcurrent state into desired state • Example • Replication Controllers Observe Act
- 49. ‹#› @tpryan Controllers • Handle turningcurrent state into desired state • Example • Replication Controllers Observe Diff Act
- 50. ‹#› @tpryan Service • Defines aset of pods that work together for a common purpose • Gets a virtual IP address • Used for exposing an application to non Kubernetes clients Virtual IP address
- 51. ‹#› @tpryan Labels & Selectors •Metadata for Objects • Select sections of your infrastructure App Tier Env todo frontend stage App Tier Env todo frontend prod App Tier Env todo frontend dev App Tier Env todo frontend test App Tier Env todo api prod App Tier Env todo backend prod App Tier Env todo api stage App Tier Env todo api test App Tier Env todo api dev App Tier Env todo backend stage App Tier Env todo backend test App Tier Env todo backend dev
- 52. ‹#› @tpryan Labels & Selectors •Metadata for Objects • Select sections of your infrastructure App Tier Env todo frontend stage App Tier Env todo frontend prod App Tier Env todo frontend dev App Tier Env todo frontend test App Tier Env todo api prod App Tier Env todo backend prod App Tier Env todo api stage App Tier Env todo api test App Tier Env todo api dev App Tier Env todo backend stage App Tier Env todo backend test App Tier Env todo backend dev
- 53. ‹#› @tpryan Labels & Selectors •Metadata for Objects • Select sections of your infrastructure App Tier Env todo frontend stage App Tier Env todo frontend prod App Tier Env todo frontend dev App Tier Env todo frontend test App Tier Env todo api prod App Tier Env todo backend prod App Tier Env todo api stage App Tier Env todo api test App Tier Env todo api dev App Tier Env todo backend stage App Tier Env todo backend test App Tier Env todo backend dev
- 54. ‹#› @tpryan Labels & Selectors •Metadata for Objects • Select sections of your infrastructure App Tier Env todo frontend stage App Tier Env todo frontend prod App Tier Env todo frontend dev App Tier Env todo frontend test App Tier Env todo api prod App Tier Env todo backend prod App Tier Env todo api stage App Tier Env todo api test App Tier Env todo api dev App Tier Env todo backend stage App Tier Env todo backend test App Tier Env todo backend dev
- 55.
- 56. ‹#› @tpryan There’s More • Secrets •Rolling Updates • Persistent Volumes
- 57. ‹#› @tpryan 03 Container Engine HostedKubernetes
- 58. ‹#› @tpryan I’ve mostly talkedabout developing on Kubernetes
- 59. ‹#› @tpryan Setting up acluster
- 60. ‹#› @tpryan Setting up acluster • Choose a cloud: • GCE, AWS, Azure, Rackspace, on-premises, …
- 61. ‹#› @tpryan Setting up acluster • Choose a cloud: • GCE, AWS, Azure, Rackspace, on-premises, … • Choose a node OS: • CoreOS, Atomic, RHEL, Debian, CentOS, Ubuntu, ...
- 62. ‹#› @tpryan Setting up acluster • Choose a cloud: • GCE, AWS, Azure, Rackspace, on-premises, … • Choose a node OS: • CoreOS, Atomic, RHEL, Debian, CentOS, Ubuntu, ... • Provision machines: • Boot VMs, install and run kube components, ...
- 63. ‹#› @tpryan Setting up acluster • Choose a cloud: • GCE, AWS, Azure, Rackspace, on-premises, … • Choose a node OS: • CoreOS, Atomic, RHEL, Debian, CentOS, Ubuntu, ... • Provision machines: • Boot VMs, install and run kube components, ... • Configure networking: • IP ranges for Pods, Services, SDN, ...
- 64. ‹#› @tpryan Setting up acluster • Choose a cloud: • GCE, AWS, Azure, Rackspace, on-premises, … • Choose a node OS: • CoreOS, Atomic, RHEL, Debian, CentOS, Ubuntu, ... • Provision machines: • Boot VMs, install and run kube components, ... • Configure networking: • IP ranges for Pods, Services, SDN, ... • Start cluster services: • DNS, logging, monitoring, ...
- 65. ‹#› @tpryan Setting up acluster • Choose a cloud: • GCE, AWS, Azure, Rackspace, on-premises, … • Choose a node OS: • CoreOS, Atomic, RHEL, Debian, CentOS, Ubuntu, ... • Provision machines: • Boot VMs, install and run kube components, ... • Configure networking: • IP ranges for Pods, Services, SDN, ... • Start cluster services: • DNS, logging, monitoring, ... • Manage nodes: • kernel upgrades, OS updates, hardware failures...
- 66.
- 67.
- 68.
- 69.
- 70. ‹#› @tpryan Container Engine • HostedKubernetes
- 71. ‹#› @tpryan Container Engine • HostedKubernetes • A few smart defaults set
- 72. ‹#› @tpryan Container Engine • HostedKubernetes • A few smart defaults set • Allow for dipping your feet in
- 73.
- 74. Google has beendeveloping and using containers to manage our applications for over 10 years.
- 75.
- 76. ‹#› @tpryan Everything at Googleruns on Containers: • Gmail, Web Search, Maps, ... • MapReduce, batch, ... • GFS, Colossus, ... • Even Google’s Cloud Platform: VMs run in containers!
- 77. ‹#› @tpryan Everything at Googleruns on Containers: • Gmail, Web Search, Maps, ... • MapReduce, batch, ... • GFS, Colossus, ... • Even Google’s Cloud Platform: VMs run in containers! We launch 2 Billion Containers a week
- 78. ‹#› @tpryan We think containersare the way to manage scale.
- 79. ‹#› @tpryan You should carefullyconsider whether running everything on containers is right for you.
- 80. ‹#› @tpryan You should runeverything on containers. Just in case it isn’t clear here. this is not what I am recommending. I’m saying don’t Cherry Pick from the last statements to come to the conclusion that you have to go this way.
- 81. ‹#› @tpryan Container Engine canmake dipping your toes in a little easier.
- 82. ‹#› @tpryan Thank You terrenceryan.com @tpryan This preso:http://bit.ly/tpryan-chaos