容器化後，持續交付不可缺的敲門磚 - Helm
•
11 j'aime•735 vues
DevOpsDays Taipei 2018 容器化後，持續交付不可缺的敲門磚 - Helm
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à 容器化後，持續交付不可缺的敲門磚 - Helm
Similaire à 容器化後，持續交付不可缺的敲門磚 - Helm (20)
Dernier
Dernier (20)
容器化後，持續交付不可缺的敲門磚 - Helm
- 2. Hello! 陳宏彥 (Zz Chen) chy168@gmail.com Kidscrape, co-founder / CTO Taipei HashiCorp User Group, co-organizer 2
- 4. 4 https://github.com/Taipei-HUG/workshop 實戰工作坊 Infrastructure as Code Terraform ❤ AWS EKS 09/15 -> 10/06
- 5. 大綱 - 故事背景 - Helm 介紹 - 導入案例 - 未來發展 5
- 6. 故事的開始 ... 6
- 8. ● 技術負責人願意嘗試導入 ● Terraform ○ VMs ○ Network ● Ansible ○ Packages ○ Code Deployment ● Google Cloud Background GCP Compute Engine Multiple Instances Cloud Load Balancing Compute Engine 8
- 9. Problems ● Many VMs ● Configurations with environments ○ beta, staging, production ○ MySQL, Redis, Cassandra, MongoDB .. etc ● Cost much time to deploy ● Struggle with local development Created by Aopsan - Freepik.com 9
- 11. ● Containerized ○ 10 Components ○ 35 Workers ○ 30 Jobs ● Migrate to kubernetes Objectives Compute Engine Kubernetes Engine 11
- 13. Pros ● Fast code deployment and rolling upgrade ● K8s managed resource ○ Ingress (LoadBalancer, SSL) ○ Less Terraform ● Decouple configurations ○ redis-dev, redis-beta, redis-prod => k8s service ○ redis-service => In Image Pros & Cons 13 Cons ● Bunch of k8s manifests ○ YAMLs x Environments ● Deployment knowledge ○ manifest creation order, parameters
- 14. How we work with k8s? 14
- 16. Nginx deployment Nginx service Nginx ingress Application 1 deployment Application 1 service Application 1 ingressworker deployment cronjobs 16
- 17. 17
- 18. Nginx deployment kubectl create -f kubectl apply -f Nginx service kubectl create -f kubectl apply -f Ingress kubectl create -f kubectl apply -f Application 1 kubectl create -f kubectl apply -f Application 2 kubectl create -f kubectl apply -f Application 2 kubectl create -f kubectl apply -f 18
- 19. Designed by Kues / Freepik 19
- 20. Helm 20
- 21. Helm is a package manager Homebrew / Apt / Yum / Portage ... 21
- 22. Helm is ... ● Template engine ● Release management ● Portability & easy onboard ● Repository hosting ● Versioning & dependency ● No more `kubectl apply` Management Repository Easy Update Release 22
- 23. Chart Repository Packaged k8s resources ReleaseChart Stored & packaged charts Deployed instance of a chart 23
- 24. Two Components Kubernetes Cluster Tiller Pod Helm Client K8S Master Nginx Deployment API Deployment MySQL Deployment 24
- 25. $ helm install nginx Releases Management $ helm upgrade $ helm rollback $ helm history Nginx Chart Release #3 Release #2 Release #1 install $ helm install 25
- 26. $ helm create CHART_NAME $ helm create devopsdays-taipei2018 26 Chart creating
- 30. template func 30
- 31. defined template call it render result 31
- 32. DEMO Let’s Helming in 5 mins! 32
- 33. ● if we have workers ... ○ make-money ○ count-money ○ push-notification ○ statistics ○ ..... An Example 自製 worker generator (簡化管理複雜度) 33
- 34. 34
- 35. Worker generator define common.worker template & iterate by `.Values.workers` 35
- 38. Daily Use of Helm Workflow, Pipeline and Testing 38
- 39. DevOps Chart Repository & git Kubernetes Cluster Nginx Deployment API Deployment MySQL Deployment Docker Image Registry & git Deveoper CI/CD Tool Nginx Deployment API Deployment MySQL Deployment production devloping values-prod.yaml values-dev.yaml 39
- 40. Comparison V1 V2 V3 Runtime VM Kubernetes Kubernetes Infra Terraform Terraform Terraform Config Management Ansible Ansible Ansible Build Image N/A Packer Packer Deployment Ansible (kubectl apply)+ helm upgrade Deployment Time 3~5m 3m ~30sec Cost 900 USD 350 USD 350 USD Instances 30 3 3 40
- 41. Comparison of Code Lines Tools V1 V2 V3 Image Ansible 2070 1351 1351 Packer N/A 972 972 Total (Build Image) 2070 2323 2323 Infra Terraform 1663 ~100 ~100 K8s Manifest N/A 2045 Helm N/A N/A 2053 Total (Infra) 1663 2145 2153 Total 3733 4468 4476 41
- 42. ● High portability ● Switch environments easily ● Decouple phased config/image ● Reusable for same type deployment (worker, jobs ... etc) ● Version control for deployment Advantages 42
- 43. Disadvantages ● Helm ○ Hard to troubleshoot ■ No diff ■ Tiller upgrade failed without error ■ Generate full k8s Manifest ○ => Helm 3 ● For team ○ Need to know Helm/k8s ○ Gap between Engineer and DevOps ■ Still need DevOps efforts ○ Who can deploy? How to trigger? ○ Who write the Chart? ○ => GitOps 43
- 44. Helm 3 44
- 45. Helm 2.x ● Template syntax hard to read & poor documentation ● Immutable variables, confusing data types, restrictive scoping ● Cannot define function in template ● Resources created by hooks are NOT managed 45
- 46. New in Helm 3 ● Lua as embedded scripting language ○ Scripts are stored in charts ● No more Tiller ○ Security enhancement ○ New Helm controller ● Hooks can be managed ● Pull-based DevOps workflow with Helm controller 46
- 47. 容器化了，然後呢？ Helm 可以說是 GitOps 敲門磚 47
- 49. GitOps 潮流 ● Draft ● Flux ● Gitkube ● Helm 3 ● Jenkins X ● Knative ● Skaffold They all support Helm 49
- 50. 50https://github.com/kubernetes/kubernetes/pull/68428 Powered by kubernetes/test-infra
- 51. Key Takeaways ● Containerized and migrate to kubernetes, refactor by Helm ○ Save money, Increase productivity ○ Reduce deployment time ○ Release management ● Key to the future, Helm 3 and GitOps 51
- 52. 謝謝 52