Continuous Delivery of Containers with Drone & Kontena

Flying with Drone
CONTINUOUS DELIVERY · BUILT ON DOCKER
Jussi Nummelin, Engineer@Kontena
@JNummelin

Container pipeline
© 2015 Kontena, Inc.
Test
• Run dependencies
• Run tests
Build
• Docker build
• Docker push
Deploy
• Launch new
containers
• Register to LB
• Remove old container
• Remove from LB

What is Kontena?
Open Source container platform built to
maximize developer happiness. Works on
any cloud, easy to setup, simple to use.

All Batteries Included!
Built-In Image Registry
Sometimes projects can not use publicly
hosted container image registries like
DockerHub. Kontena comes with built-in
container image registry providing private and
secure solution.
Built-In VPN Access
All containers are run inside a virtual private
network by default. Nothing is exposed to
Internet unless explicitly defined. With
Kontena’s built-in VPN access developers can
securely access those resources.
Built-In Load Balancer
Kontena comes with built-in load balancer.
Based on Haproxy. It features fully automatic,
zero-downtime operation due to deep
integration with Kontena’s service discovery
and orchestration technology.
Aggregated Stats & Logs
Kontena provides real-time log and statistics
streams containers. The streams may be
grouped and aggregated to produce service
level streams. This allows easy viewing of logs
and statistics for your application CPU,
memory, disk and network usage.
User Management with Audit Trail
All events and actions performed through
Kontena CLI or APIs are logged into audit trail.
Combined with users and access control, the
audit trail support makes Kontena a reliable
and secure solution for any enterprise
deployments.
Built-In Secrets Management
When your application requires access to APIs
or databases, you'll often need to use secrets
such as passwords and access tokens for
authenticating the access. Kontena Vault is a
secure key/value storage that can be used to
manage secrets in Kontena.

“Includes all the sh*t you don’t need to
implement by yourself”

What is Drone?
•Docker based CI/CD platform
•Easy to install & maintain
•Isolated builds (Docker containers)
•Pluggable (Docker containers)
•Integrates to Github / Gitlab and others
•Travis like “just works” feeling

Why should I care?

Agility matters

Why Should I Care?
•Lightweight, low memory footprint
•Single binary, written in Go
•Docker native
•Simple YAML configuration
•Supports any language that can run in Docker

Installation
•Single binary, just execute
•Docker image (preferred way)
•Configuration through environment variables
•0.5 introduced build agents, easy to scale

Installation: The Docker Way
$ docker run -d
-v /var/lib/drone:/var/lib/drone
-v /var/run/docker.sock:/var/run/docker.sock
--env-file /etc/drone/dronerc
--restart=always --publish=80:8000
--detach=true --name=drone
drone/drone:0.4

Installation: The Kontena Way
server:
image: drone/drone:0.5
instances: 1
stateful: true
deploy:
strategy: ha
wait_for_port: 80
ports:
- 8080:80
environment:
- DRONE_DEBUG=true
- DRONE_GITHUB=true
- DRONE_SERVER_ADDR=0.0.0.0:80
- DRONE_OPEN=true
- DATABASE_DRIVER=sqlite3
- DATABASE_CONFIG=/var/lib/drone/drone.sqlite
secrets:
- secret: DRONE_GITHUB_CLIENT_ID
name: DRONE_GITHUB_CLIENT
type: env
....
volumes:
- /var/lib/drone
agent:
image: drone/drone:0.5
stateful: no
instances: 3
depends_on:
- server
environment:
- DRONE_DEBUG=true
- DRONE_SERVER=http://%{project}-server:80
secrets:
- secret: DRONE_SHARED_SECRET
name: DRONE_SECRET
type: env
volumes:
- /var/run/docker.sock:/var/run/docker.sock
command: agent

Configuration
•Remote driver
• Bitbucket, Github, Gitlab, Gogs
•Database
• SQLite (default), Postgres, MySQL

Concepts – the “.drone.yml”
•Plugins
•Pipeline
•Services
•Matrix
•Secrets
•Constraints

Concepts - Plugins
• Plugin is actually just a Docker image
• Container created and executed part of pipeline
• Exit code determines success/failure
pipeline:
test:
image: ruby:2.3
commands:
- bundle install --path=bundler
- rspec spec/

Concepts – Pipeline
•Arbitrary set of “plugins” to run as the build process
•Success determined by exit code
•Defined in .drone.yml

Concepts -- Services
• Set of services needed in the build process
• Available on the same network namespace as build containers
• Handy for eg. Databases used in testing

Concepts – Matrix
• Build a single commit against many configurations
• Interpolated as variables in yaml parsing

Concepts – Matrix
pipeline:
build:
image: golang:${GO_VERSION}
commands:
- go get
- go build
- go test
services:
database:
image: ${DATABASE}
matrix:
GO_VERSION:
- 1.4
- 1.3
DATABASE:
- mysql:5.5
- mysql:6.5
- mariadb:10.1

Concepts – Secrets
• Keep your secrets out of VCS
• Injected into build containers
• Available in the env
• Available only to specific container in build
• Leak radius

Concepts – Secrets
$ drone secret ls jnummelin/todo-example
DOCKER_USERNAME
Images: plugins/docker
Events: push, tag, deployment
DOCKER_PASSWORD
DOCKER_EMAIL
KONTENA_TOKEN
Images: jnummelin/kontena-cli
KONTENA_URL
KONTENA_GRID

Concepts – Constraints
• Limit execution of build steps at runtime
• Branches: [master, develop]
• Events: tag, push, pull_request, …
• Platform: [ linux/*, windows/amd64 ]
• “Deploy when pushed to master” type of things

git push
webhook
docker push
dockerpull
status

Links
• https://github.com/jnummelin/todo-example
• http://readme.drone.io/0.5/usage/overview/
• https://www.meetup.com/Kontena-NYC/
• https://kontena.io/docs/

$25 Credits for Testing
https://www.packet.net/promo/kontena/

We are hiring!
kontena.io/jobs

Continuous Delivery of Containers with Drone & Kontena

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Continuous Delivery of Containers with Drone & Kontena

Similar to Continuous Delivery of Containers with Drone & Kontena (20)

Recently uploaded

Recently uploaded (20)

Continuous Delivery of Containers with Drone & Kontena