CD, Docker and Kubernetes

MartinPodval

Building Pipeline

● Artifacts: Docker images

● Same GIT revision

● Fail immediately, fully

automatic

Share Reasonable Amount of CodeAn architecture is based on …

… autonomous services

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

Branching Strategy

● Every change can end in

the production

● Do not block following

changes

Kubernetes?

Revolutionary open source cluster container management:

● Manages docker containers located somewhere in the cluster

● By Google; IBM, RedHat, MS or Mesosphere also contribute

Kubernetes? Cont’d

Infrastructure glue, you don’t want to develop

● Guarantees eventually consensual environment● Simplifies:

○ Development○ Deployment○ Operations

You can see a cluster …

… as separated machines

… or as a single resource pool

Indirection Levels

How can it help you with CD?

● Pod● RC● Service

>kubectl create -f -

Rolling Updates

● Update a service to a new version● The service is still available● Replaces running docker containers in fact

>kubectl rolling-update v2

Rolling Updates Cont’dReplication controller continually changes one pod at a time

©crsmnky

Q & A