Download as PDF, PPTX
Uploaded byLuke Marsden
Continuous Delivery the hard way with Kubernetes
The document discusses continuous delivery using Kubernetes and GitLab, outlining the benefits, including improved team velocity and microservices scalability. It covers the fundamentals of Kubernetes components such as pods, services, and deployments, while also detailing a version-controlled configuration approach for managing deployments. Finally, it highlights the transition to a release manager architecture to enhance deployment processes and rollback capabilities.
More Related Content
Similar to Continuous Delivery the hard way with Kubernetes
![Automating ISP Networks Using Ansible and IPAM as a Source of Truth [SoT]](https://cdn.slidesharecdn.com/ss_thumbnails/automatingispnetworksusingansibleandipamasasourceoftruthsot-v25-1-251124105117-d7d4ca24-thumbnail.jpg?width=640&height=640&fit=bounds)
Continuous Delivery the hard way with Kubernetes
- 1. Continuous Delivery thehard way with Kubernetes Luke Marsden, Developer Experience @lmarsden
- 2. Agenda 1. Why shouldI deliver continuously? 2. Kubernetes primer 3. GitLab primer 4. “OK, so we’ve got these pieces, how are we going to put them together?” 5. Let’s iterate on a design! 6. Conclusions
- 3. Agenda 1. Why shouldI deliver continuously? 2. Kubernetes primer 3. GitLab primer 4. “OK, so we’ve got these pieces, how are we going to put them together?” 5. Let’s iterate on a design! 6. Conclusions
- 4. Why should Icontinuously deliver? • Microservices • Conway’s law • Scaling project, scaling team • Velocity!
- 5. Kubernetes: all youneed to know Pods containers ServicesDeployments Container Image Docker container image, contains your application code in an isolated environment. Pod A set of containers, sharing network namespace and local volumes, co-scheduled on one machine. Mortal. Has pod IP. Has labels. Deployment Specify how many replicas of a pod should run in a cluster. Then ensures that many are running across the cluster. Has labels. Service Names things in DNS. Gets virtual IP. Two types: ClusterIP for internal services, NodePort for publishing to outside. Routes based on labels.
- 6. GitLab primer • Oryou can use GitHub, Travis, Circle, Docker Hub, Quay.io, GCR… CI system Docker registry GitLab Version controlled code Version controlled code
- 7. Version controlled code These are thethings that we’ve got Version controlled code CI system Docker registry Kubernetes clusterCode Docker image Kubernetes YAML
- 8. Version controlled code These are thethings that we’ve got Version controlled code CI system Docker registry Kubernetes clusterCode Docker image Kubernetes YAML git git + shell docker registry API kubernetes API
- 9. These are thethings that we’ve got Version controlled code CI system Docker registry Kubernetes clusterCode Docker image Kubernetes YAML
- 10.
- 11.
- 12.
- 13. V1 Deploy update (withCI system)
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21. Version controlled code V1 architecture Version controlled code CI system Docker registry Kubernetes cluster gitcheckout master git revert HEAD git push
- 22.
- 23.
- 24.
- 25.
- 26. Downsides • Building &pushing containers is slow (disk I/O, network), shouldn’t need to this when rolling back • Branch per environment required per microservice (explosion of branches, hard to manage & scale) • Only a matter of time until you get a git merge mess • Better to decouple version of code at HEAD from version deployed…
- 27. Version controlled configuration •users service • code for users service • Kubernetes YAML • orders service • code for orders service • Kubernetes YAML • config repo • Kubernetes YAML for users • Kubernetes YAML for orders • Version controlled config should be the source of truth for your whole app (all the microservices)
- 28. Decoupling versions fromreleases Code versions (branches, tags) Environments & releases • users service • master • feature_A • feature_B • orders service • master • feature_A • feature_B • … • production • users -> master @ t1 • orders -> master @ t1 • staging • orders -> master @ t2 • orders -> master @ t2 conflating per- service code branches with environments in each repo is a hack, and doesn’t scale well
- 29. V2 Put all theyamels in one place
- 30. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 31. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 32. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 33. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 34. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 35. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 36. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 37. Version controlled code V2 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Code Dockerimage Kubernetes YAML Have the CI system update the yamels automatically for you
- 38. Version controlled code Container builder demo Version controlled code CIsystem Docker registry Kubernetes cluster Version controlled config Code Docker image Kubernetes YAML Have the CI system update the yamels automatically for you Builder used as CD system
- 39. Now you canrecreate your production environment from the central YAML repository even if your entire production cluster gets deleted
- 40.
- 41. Downsides • The CIsystem is responsible for a lot now (design smell – overloaded) • You can only trigger the CI system by pushing code (we wanted to be able to rollback without pushing code) • If you rollback out of band (directly with kubectl), you have to remember to update the central configuration repo as well • Parallel builds can tread on eachothers’ toes, not atomic: race between git checkout and git push (need a global lock) • Scripting updates of yamels can be a pain… it mangles your yamels • Developers start asking for more release management features (rollback, pinning, automation for some envs and manual gating for others, and your once-simple script keeps growing…)
- 42.
- 43. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 44. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 45. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 46. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 47. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 48. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 49. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 50. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy
- 51. V3 Rollback doesn’t govia CI
- 52. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy rollback!
- 53. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy rollback!
- 54. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy rollback!
- 55. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy rollback!
- 56. Version controlled code V3 architecture Version controlled code CI system Docker registry Kubernetes cluster Version controlled config Release manager Code Dockerimage Kubernetes YAML push im age push config pull image list images pull, modify, push config push code policy rollback!
- 57. What does therelease manager do? • Watches for changes in a container registry (output of CI system) • Makes commits for you to version controlled configuration (understands Kubernetes YAML) • Depending on release policy (per environment), either push changes continuously or permit manually gated releases • Allows releases to be rolled back by changing a pointer • Releases can be “locked” as a social cue
- 58. Different environments canhave different release policies (no tight coupling between individual microservices repos and what’s released)
- 59.
- 60. This is howwe deploy Weave Cloud Weave Cloud helps devops iterate faster with: • observability & monitoring • continuous delivery • container networks & firewalls Weave Flux is a release manager for Kubernetes
- 61. Other topics • Kubernetes101 • How do I monitor this stuff? (Prometheus) • Network policy for isolating & firewalling different microservices We have talks & trainings on all these topics in the Weave user group!
- 62. Join the Weaveuser group! meetup.com/pro/Weave/ Come hang out on Slack! weave.works/help
- 63. Thanks! Questions? We arehiring! DX in San Francisco Engineers in London & SF weave.works/weave-company/hiring Check out Flux on GitHub: github.com/weaveworks/flux