From local servers up to Kubernetes in the cloud
0 likes153 views
This document discusses transitioning from local servers to cloud infrastructure and containerization using Kubernetes. It begins with an overview of infrastructure as a service (IAAS) benefits like hardware failure proofing and on-demand resources. It then discusses containerizing applications for portability and faster deployments. Finally, it outlines orchestrating containers with Kubernetes to automatically scale applications and maintain high availability. The document proposes these transitions to improve time to market, costs, and focus on development rather than operations. It acknowledges challenges around networking, configuration, and volumes that containers and orchestration address.
From local servers up to Kubernetes in the cloud
- 2. TO THE CLOUD… From local servers up to Kubernetes in the cloud Reasons why
- 3. DISCLAIMER
- 6. FROM LOCAL SERVERS TO IAAS 1 1 2 3
- 7. IAAS OVERVIEW Software layer Virtual machines On-demand (API & UI) 1 2 3 Hardware failure proof
- 8. TRANSITION CONTEXT Dead servers Power off Manual scale out Overnight incidents Mutualize resources Ops’ daily mission Deploy new versions 1 2 3
- 9. TRANSITION BENEFITS Privacy Shorten time to market Finance Stronger SLA On-demand production environment Set the focus on developing user-value 1 2 3
- 10. POST-TRANSITION ASSETS On-demand environment provisioning code Virtual machines provisioning Application deployment 1 2 3
- 11. TRANSITION INHIBITORS Ad-hoc provisioning Virtualization: potential performance impact No real control on hardware 1 2 3
- 12. FROM IAAS TO CONTAINERS 2 1 2 3
- 13. CONTAINER OVERVIEW Complete Shareable Image Immutable Isolated 1 2 3 Ready to use Portability Light
- 14. TRANSITION CONTEXT Incompatibility between software components Time consuming integration & deployment Complex local environment 1 2 3
- 15. TRANSITION BENEFITS Software diversity Faster CI/CD Foster modularity Close to production environment 1 2 3
- 16. POST-TRANSITION ASSETS Modular & distributed software architecture Containerised CI/CD Container images library 1 2 3
- 17. INHIBITORS Container network Adapting configuration Persisting volume Containers number growing up… 1 2 3
- 19. ORCHESTRATION OVERVIEW Distributes & runs replicas over available machines Knows all available infrastructure resources Maintain application latency, no matter the workload Also a nurse for my application Creates replicas of the containerized application 1 2 3
- 20. TRANSITION CONTEXT Existing code/tools to provision VMs & deploy containerised services Manual distribution of services within VMs Ad-hoc & non-scalable architecture 1 2 3
- 21. BENEFITS Application automatic scale-out with workload Lighten even more Ops workload Keep application up & running 24/7 (high availability) Save money, maximizing usage of CPU 1 2 3
- 22. ASSETS An application that can be deployed over a dynamic infrastructure A resilient application (kept up & running) Update application with no down-time Capability to tune scaling out criteria of my application 1 2 3
- 23. INHIBITORS Route external traffic to applications Configure Container network interface Manage shared persisting volumes 1 2 3
- 24. KAPSULE
- 25. WHAAT’S THAT ? Cluster creation in no time ! Leveraging Scaleway instances portfolio ! Multiple CNI plug-ins deployment Route external traffic with Ingress Controller or LB 1 2 3 Managed Kubernetes service Kubernetes 1.13 1.14
- 26. MERCI Suivez notre actualité, tutoriels inédits et infos cloud sur Twitter et LinkedIn @Scaleway Et suivez-moi sur LinkedIn @michaël-mérignargues