Download as PDF, PPTX
![STORY
Go + Kubernetes
SMACC - Fintech / ML - [10.2017- ...]
Lyke - Mobile Fashion app - [12.2016, 07.2017]](https://image.slidesharecdn.com/index-181128060109/85/Zero-downtime-deployment-of-micro-services-with-Kubernetes-3-320.jpg)
![STORY
Lyke - [12.2016 - 07.2017]
SMACC - [10.2017 - present]](https://image.slidesharecdn.com/index-181128060109/85/Zero-downtime-deployment-of-micro-services-with-Kubernetes-57-320.jpg)
Uploaded byWojciech Barczyński
Zero downtime deployment of micro-services with Kubernetes
The document discusses zero downtime deployment strategies using Kubernetes, focusing on methods such as rolling updates, blue-green deployment, and canary releases. It outlines essential Kubernetes components like pods, services, and deployment strategies, emphasizing the importance of implementing readiness and liveness probes for maintaining service stability. Additionally, it highlights a practical example involving the deployment of a demo API and the functionality of various deployment strategies within Kubernetes.
More Related Content
Similar to Zero downtime deployment of micro-services with Kubernetes
![Effective Kubernetes == Keep it Simple [Ignite Talk DevOpsDays Warsaw]](https://cdn.slidesharecdn.com/ss_thumbnails/slides-181120223017-thumbnail.jpg?width=640&height=640&fit=bounds)
Zero downtime deployment of micro-services with Kubernetes
- 1. ZERO DOWNTIME DEPLOYMENT STRATEGIESWITH K8S + HOW TO PREPARE YOUR SERVICE Wojciech Barczynski - SMACC.io | Hypatos.ai Listopad 2018
- 2. WOJCIECH BARCZYŃSKI Lead Soware Engineer & System Engineer Interests: working so ware Hobby: teaching so ware engineering and programming
- 3. STORY Go + Kubernetes SMACC- Fintech / ML - [10.2017- ...] Lyke - Mobile Fashion app - [12.2016, 07.2017]
- 8. KUBERNETES Learn-as-you-go Battery for 12factor apps ...appmust be smarter
- 9. KUBERNETES Kubernetes Node Node Node Node App Ingress Controller Repository make docker_push;kubectl create -f app-srv-dpl.yaml
- 10. SCALE UP! SCALEDOWN! Kubernetes Node Node Node Node App Ingress Controller App Appscale 3x kubectl --replicas=3 -f app-srv-dpl.yaml
- 11. DEPLOYMENT AND PODS Node Master Deployment Dockercontainers Node Docker Containers Pod Schedule Schedule
- 12. DEPLOYMENT.YML apiVersion: apps/v1 kind: Deployment metadata: name:demo-api labels: app: demo-api spec: replicas: 3 strategy: type: Recreate selector: matchLabels: app: demo-api template: metadata:
- 13. SERVICE AND PODS Node Deployment Pod Node Pod services Fixedvirtual address Fixed DNS entry Service matches pods based on labels
- 14. SERVICE.YML apiVersion: v1 kind: Service metadata: name:demo-api spec: ports: - port: 80 protocol: TCP selector: app: demo-api type: LoadBalancer
- 15. BASIC CONCEPTS Name Purpose ServiceInterface Entry point (Service Name) Deployment Factory How many pods, which pods Pod Implementation 1+ docker running
- 16. HOW GET USERREQUESTS? API BACKOFFICE 1 DATA WEB ADMIN BACKOFFICE 2 BACKOFFICE 3 API.DOMAIN.COM DOMAIN.COM/WEB BACKOFFICE.DOMAIN.COM ORCHESTRATOR PRIVATE NETWORKINTERNET API LISTEN (DOCKER, SWARM, MESOS...) Ingress Controller
- 17. INGRESS Pattern Target AppService api.smacc.io/v1/users users-v1 api.smacc.io/v2/users users-v2 smacc.io web
- 18. SERVICE DISCOVERY AND LABELING namesin DNS: curl labels: name=value annotations: prometheus.io/scrape: "true" http://users/list
- 19.
- 20. STRATEGIES We will see: Replace(downtime visible) Rolling updates Blue Green Canary
- 21. OTHER We will notcover: Feature toggles A/B like Shadow deployment
- 22. FIRST THE HOMEWORK Needto support: liveness - am I dead? readiness - can I serve requests?
- 23. KUBE LIVENESS PROBE livenessProbe: httpGet: path:/model port: 8000 httpHeaders: - name: X-Custom-Header value: Awesome initialDelaySeconds: 600 periodSeconds: 5 timeoutSeconds: 18 successThreshold: 1 failureThreshold: 3
- 24. LIVENESS PROBE our podgets restarted too many restarts -> CrashLoop
- 25. KUBE READINESS PROBE readinessProbe: exec: command: -cat - /tmp/healthy initialDelaySeconds: 5 periodSeconds: 5
- 26. YOUR APP SHOULDON STOP 1. we get SIGTERM signal
- 27. YOUR APP SHOULDON STOP 1. we get SIGTERM signal 2. app gives 500 on readinessProbe
- 28. YOUR APP SHOULDON STOP 1. we get SIGTERM signal 2. app gives 500 on readinessProbe 3. k8s does not send more requests
- 29. YOUR APP SHOULDON STOP 1. we get SIGTERM signal 2. app gives 500 on readinessProbe 3. k8s does not send more requests 4. app shuts down gracefully
- 30. YOUR APP SHOULDON STOP 1. we get SIGTERM signal 2. app gives 500 on readinessProbe 3. k8s does not send more requests 4. app shuts down gracefully 5. kuberenetes forces kill if 30s limit exceeded
- 31. ALWAYS Implement readiness for: MLModel-based components slow starting time
- 32. DEMO SERVICE IMPLEMENTATION gracefulshutdown demo service
- 33. GRACEFUL SHUTDOWN From :missy func(s *Service) prepareShutdown(h Server) { signal.Notify(s.Stop, os.Interrupt, syscall.SIGTERM) <-s.Stop s.StatusNotReady() shutdown(h) }
- 34.
- 35. DEMO - RECREATE spec: replicas:3 strategy: type: Recreate kubectl set image deployment/demo-api app=wojciech11/api-status:2.0.0
- 36.
- 37. DEMO - ROLLINGUPDATES Service Pods Labels Service Pods Labels v1 v1 v1 v1 v1 v2
- 38. DEMO - ROLLINGUPDATES strategy: type: RollingUpdate rollingUpdate: maxSurge: 2 maxUnavailable: 0 docs
- 39. DEMO - ROLLINGUPDATES kubectl set image deployment/demo-api app=wojciech11/api-status:2.0.0
- 40. DEMO - ROLLINGUPDATES the most popular
- 41.
- 42.
- 43. DEMO - GREEN/BLUE kubectlpatch service api-status -p '{"spec":{"selector": {"label": "green"} }}'
- 44. DEMO - GREEN/BLUE Forbig changes Less common Might be implemented with Ingress
- 45.
- 46.
- 47.
- 48.
- 49.
- 50. kubectl scale --replicas=3deploy/api-status-nginx-blue kubectl scale --replicas=1 deploy/api-status-nginx-green # no errors, let's continoue kubectl scale --replicas=2 deploy/api-status-nginx-blue kubectl scale --replicas=2 deploy/api-status-nginx-green
- 51. TRAEFIK apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: traefik.ingress.kubernetes.io/service-weights:| my-app: 99% my-app-canary: 1% name: my-app spec: rules: - http: paths: - backend: serviceName: my-app servicePort: 80 traffic-splitting
- 52. ISTIO apiVersion: networking.istio.io/v1alpha3 kind: VirtualService metadata: name:helloworld spec: hosts: - helloworld http: - route: - destination: host: helloworld subset: v1 weight: 90 - destination: host: helloworld traffic shi ing with Istio
- 53. SUMMARY learn-as-you go <3 easyto implement complex strategies see kubectl rollout and minReadySeconds for more control
- 54.
- 56.
- 57. STORY Lyke - [12.2016- 07.2017] SMACC - [10.2017 - present]
- 59. LYKE Now JollyChic Indonesia E-commerce Mobile-only 50k+users 2M downloads Top 10 Fashion Apps w Google Play Store http://www.news.getlyke.com/single- post/2016/12/02/Introducing-the- New-Beautiful-LYKE
- 60. GOOD PARTS Fast Growth A/BTesting Data-driven Product Manager, UI Designer, Mobile Dev, and tester - one body
- 61. CHALLENGES 50+ VMs inAmazon, 1 VM - 1 App, idle machine Puppet, hilarious (manual) deployment process Fear Forgotten components sometimes performance issues
- 63. SMACC Machine Learning FinTech SaaSand API platform From Enterprise (Deutsche Bank, AoK) to SME Well-known FinTech Startup in Germany
- 64. STORY Legacy on AWS,experiments with AWS ECS :/ Self-hosted K8S on ProfitBricks Get to Microso ScaleUp, welcome Azure Luckily - Azure-Kubernetes-Service
- 65. DIFFERENCE ☠ Two teamsin Berlin and Warsaw Me in Warsaw
- 66. APPROACH Simplify, Simplify Hide K8Smagic git tag driven Continoues Deployment
- 67.
- 68. PODS See each otheron localhost Live and die together Can expose multiple ports Pod nginx WebFiles ENV: HOSTNAME=0.0.0.0 LISTENPORT=8080
- 69.
- 70.