Why we use Kubernetes at my company

This presentation was for the Singapore Oracle meetup to highlight the benefits of adopting Kubernetes but also make people aware about some challenges in Kubernetes adoption and when it might not make sense to use Kubernetes.

Transcript

1. Why we use Kubernetes at my company
2. Who am I? Vincent De Smet Site Reliability Engineer @ Swatmobile co-organise Kubernetes meetups in Singapore https://www.meetup.com/Singapore-Kubernetes-User-Group vincentdesmet so0k
3. What are Containers? • Packages up software binaries & dependencies • Immutable & testable • Isolate software from each other • Portable across environments a self-contained process ref: kubernetes-comic
4. Why Containers? image: ruby:2.1 services: - postgres stages: - Build - Test - Staging - Production ... source: GitLab CI Lightweight Reproducible builds
6. More than just packing and Isolation - Scheduling: Where should the containers run? - Resource Optimisation: How much resources does each container really need? - Monitoring: What’s happening with the containers? - Lifecycle and health: Keep containers running despite failures - Auth{n,z}: Control who can do what with the containers? - Scaling: Handle higher load by adding more instances - Discovery: How can I connect to the containers? - … Source
7. ref: kubernetes-comic
8. Kubernetes how - Declarative vs Imperative: Replicas:2 vs for(i :=0; i<2;i++){ run "replica" } - Desired state + Actual State => Convergence Concept: controllers per resource type (extensible) - One time job (native) - Cron job (native) - Long running stateless process (native) - Let's Encrypt Certificate (extension) - Reverse Proxy Virtual Route (~native)
9. Kubernetes how - Discovery of endpoints Label resources + use label queries - i.e : Find all the long running processes that can service an "orders" API request → Decouple where things are through dynamic discovery (embrace failure / change)
10. Kubernetes key features - Decouple machines from workloads - Programmable workload management (extensible resource types, autoscaling, operators, ...) - Automatic recovery through health checks - Resource optimisation through resource requests / limits - Auth{z,n} strong role-based access control and team resource allocations
11. Kubernetes caveats - Embracing failure
12. Kubernetes Must read: https://k8s.af/ here?
13. Kube Nightmare
14. Kubernetes pros - Scalable application design - Reproducible environments - Decouple server operations from application operations - Ecosystem / innovative OSS projects / great Cloud Provider support
15. Lessons learned / tips - Developer buy-in is important communication, abstractions (!), insights, dev tooling - Ops job becomes a lot more flexible if you keep state out of the cluster (cluster upgrades / migrations / failure zones / … ) - App maturity (Autoscaling) If you can't autoscale (horizontally)…. Kube may not be the right option - Do you have the resources? small startup? kube may be too much of an overhead (get support from cloud provider dedicated architects & use managed solution)
17. ref: kubernetes-comic
18. origin story Star Trek?
19. 1 2 3 4 5 6 7