KUBERNETES
PATTERNS
DevNation Tech Talk, 10/2018
Roland Huß, Red Hat, @ro14nd
" m " fo r m e n u , "? " fo r o t h e r s h o r t c u t s
KUBERNETES
Open Source container
orchestration system
Scheduling
Horizontal scaling
Self-healing
Service discovery
Rollout and Rollbacks
Declarative, resource-centric
REST API
Design Patterns
M i c h a e l M a n d i b e rg , C C BY - SA 2 . 0 , h t t p s : / / fl i c . k r /p / 67 C b 6 J m
DESIGN PATTERN
A Design Pattern describes a
repeatable solution to a
software engineering problem.
https://leanpub.com/k8spatterns
STRUCTURE
Problem
Patterns:
Name
Solution
http://www.martinfowler.com/articles/writingPatterns.html
FOUNDATIONAL
PATTERNS
Automatable Unit
How can we create and manage
applications with Kubernetes ?
Pods: Atomic unit of containers
Services: Entry point to pods
Grouping via Labels,
Annotations, Namespaces
POD
Kubernetes Atom 10.1.29.2 name: pong
version: 1
One or more
containers sharing: rhuss/pong:1
IP and ports rhuss/log-sidecar:2.3
Volumes
Ephemeral IP address
POD DECLARATION
apiVersion: v1
kind: Pod
metadata:
name: pong
labels:
name: pong
version: "1"
spec:
containers:
- image: "rhuss/pong:1"
name: pong
ports:
- containerPort: 8080
- image: "rhuss/log-sidecar:2.3"
name: log
REPLICA SET
Responsible for managing Pods
replicas : Number of Pod copies to
keep
Label selector chooses Pods
Holds a template for creating new
Pods
ReplicaSet
replicas:
3 Selector: name: pong
version: 1
10.1.29.2 10.1.29.3 10.1.29.4
name: pong name: pong name: pong
version: 1 version: 1 version: 1
SERVICE
Entrypoint for a set of Pods
Pods chosen by Label selector
Permanent IP address
10.1.29.2 10.1.29.3 10.1.29.4
name: pong name: pong name: pong
version: 1 version: 1 version: 1
10.200.100.251 Selector: name: pong
Deployment Cron Job
Replication
Daemon Set Replica Set Stateful Set Job
Controller
Pod
Horizontal Pod Container Pod Disruption
Service Ingress
Autoscaler (your code) Budget
Volume
Persistent
ConfigMap Secret
Volume Claim
Declarative
Deployment
How can applications be deployed
and updated ?
Declarative versus Imperative
deployment
Various update strategies
DEPLOYMENT
Holds template for Pod
Creates ReplicaSet on the fly
Allows rollback
Update strategies declarable
Inspired by DeploymentConfig
from OpenShift
ROLLING
v 1.0 v 1.0 v 1.0
Service
v 1.1 v 1.1
FIXED
v 1.0 v 1.0 v 1.0
Service
v 1.1 v 1.1 v 1.1
CANARY
v 1.0 v 1.0 v 1.0
Service
v 1.1
BLUE-GREEN
v 1.0 v 1.0 v 1.0
Service
v 1.1 v 1.1 v 1.1
SUMMARY
Rolling Deployment Recreate Deployment
instances instances
time time
0 … 1 capacity
Blue-Green Release Canary Release
instances instances
time time
2x capacity
STRUCTURAL
PATTERNS
Initializer
How can I initialize my containerized
applications ?
Init container :
Part of a Pod
One shot action before Pod starts
Needs to be idempotent
Has own resource requirements
Container Container
app containers
Container Container Container
init containers
Pod
Sidecar
How can I extend the functionality of
an existing container ?
Runtime collaboration of
containers
Connected via shared resources:
Network
Volumes
Main Container Sidecar
node.js git
Disk
Pod
Ambassador
How to decouple a container's
access to the outside world ?
Also known as Proxy
Specialization of a Sidecar
E.g. infrastructure services
Circuit breaker
Tracing
Container Container
python memcached
localhost
Pod
Adapter
How to decouple access to a
container from the outside world ?
Opposite of Ambassador
Uniform access to application
Examples:
Monitoring
Logging
Main Container Sidecar
java monitoring
Disk
Pod
ADVANCED
PATTERNS
Custom Controller
How can I extend the platform itself
without changing it ?
Watching resources by registering
for Kubernetes events
Reacting on changes in resource
declarations
CONTROLLER
Managed pod listening for
Kubernetes API events
State Reconciliation : Make the
current state like the declared
desired state
Often used in combination with
CustomResources
CATEGORIES
Extension Controller : Extend
the Kubernetes platform itself
Application Controller :
Combine Kubernetes with an
application specific domain
Custom Resource
How can I manage custom domain
specific resources ?
Custom Resource Definition
(CRD) managed by Kubernetes
Accessible via the Kubernetes API
Watched by Custom Controllers
EXAMPLE CRD
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: prometheuses.monitoring.coreos.com
spec:
group: monitoring.coreos.com
names:
kind: Prometheus
plural: prometheuses
scope: Namespaced
version: v1
validation: ....
EXAMPLE CRD
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
name: prometheus
spec:
serviceMonitorSelector:
matchLabels:
team: frontend
resources:
requests:
memory: 400Mi
OPERATORS
Combine Custom Controller and
Custom Resource
Manages and deploys custom
Kubernetes application
Operator Framework by CoreOS:
Operator SDK
Operator Lifecycle Manager
Operator Metering
SPECTRUM
with Custom Resource
Operator
Expose
Controller
etcd
Operator EAI
Controller
ConfigMap
Controller
Prometheus
Operator
Extension Controller Application Controller
https://leanpub.com/k8spatterns
QUESTIONS ?
Twitter ro14nd
Book https://leanpub.com/k8spatterns
Slides https://github.com/ro14nd-talks/kubernetes-patterns
