Continuous deployment, docker and kubernetes

1. CD, Docker and
Kubernetes
MartinPodval

2. Building Pipeline
● Artifacts: Docker images
● Same GIT revision
● Fail immediately, fully
automatic

3. Share Reasonable Amount of Code
An architecture is based on …
… autonomous services

4. Deploy Small Changes
● Smaller change = less number of potential problems
● Split features to small deployable steps
● Always verify the change in the production
… it is always doable

5. Branching Strategy
● Every change can end in
the production
● Do not block following
changes

7. Kubernetes?
Revolutionary open source cluster container management:
● Manages docker containers located somewhere in the
cluster
● By Google; IBM, RedHat, MS or Mesosphere also
contribute

8. Kubernetes? Cont’d
Infrastructure glue, you don’t want to develop
● Guarantees eventually consensual environment
● Simplifies:
○ Development
○ Deployment
○ Operations

9. You can see a cluster …
… as separated machines

10. … or as a single resource pool

11. Indirection Levels
How can it help you with CD?
● Pod
● RC
● Service

12. >kubectl create -f -

13. Rolling Updates
● Update a service to a new version
● The service is still available
● Replaces running docker containers in fact
>kubectl rolling-update v2

14. Rolling Updates Cont’d
Replication controller continually changes one pod at a time
©crsmnky

15. Q & A