Presentation of the Blue Harvest meetup: "Container Orchestration on AWS". This talk introduced containers and container orchestration, explained kubernetes as containers orchestrator and helm as package manager for kubernetes. Besides, we demoed the provisioning of a kubernetes cluster on AWS using a GitLab pipeline, KOPS and terraform.

1. CONTAINERS ORCHESTRATION ON AWS

2. 1. Containers and Containers orchestration
2. Kubernetes as Containers orchestrator
3. Live Demo: Kubernetes on AWS
4. Continuous Delivery on Kubernetes
5. Live Demo: CI/CD on Kubernetes
Agenda

3. 1. CONTAINERS AND CONTAINERS
ORCHESTRATION

4. Linux Containers
“Lightweight partitioning of a host operating system into isolated
spaces built on top of the Linux Kernel facilities”

5. 1979: UNIX introduced the chroot system call
2000: FreeBSD Jails
2004: Solaris containers
2006: Google process containers, later on renamed to Cgroups
2008: LXC, built on top of Cgroups and Linux namespaces
2013: Docker, built on top of LXC, changed later to libcontainer and runC
History

6. Platform independence
Operational simplicity
Smoother scaling
Developer productivity
Isolation

7. Scheduling
Autoscaling
Self-healing
Rollouts and rollbacks
Challenges

8. CONTAINERS ORCHESTRATION

9. • Elastic Container Service (ECS)
• Elastic Container Service for Kubernetes (EKS)
• Own Kubernetes setup on top of EC2
Containers Orchestration on AWS

10. 2. KUBERNETES AS CONTAINERS
ORCHESTRATOR

11. • 2014: Born at Google as an opensource version of Borg
• 2015: Kubernetes v1.0 is released as part of the CNCF
• 2016: Kubernetes goes mainstream
• 2017: The year of enterprise adoption and support
Kubernetes

12. Service
Pod Pod
Node
Ingress
……
……
Kubernetes abstractions
Deployment

13. Kubernetes networking
container 1 container 2 container 3 container 4
pod 2 (pod IP)
localhost localhost
Service
(Cluster IP)
Node 1 (Node IP)
Nodes
Network
Pods
Network
Services
Network
pod 1 (pod IP)
Node 2 (Node IP)

14. controller-
manager
API Server
etcd
Worker nodeMaster node
container
container
kube-proxy
pod (s)
scheduler
kublet

15. Availability
Zone 1
Master
Workers
Etcd
Availability
Zone 2
Master
Workers
Etcd
Availability
Zone 3
Master
Workers
Etcd

16. • What my cluster topology is going to be?
• What about networking?
• Identity and Access Management?
• Scalability?
• Visibility?
Cluster design decisions

17. TF
Code
KOPS
State
TF
State
1. KOPS 2. TERRAFORM
EC2ELB
AWS S3
3. GitLab CI/CD pipeline
kops create cluster
--dns-zone=blueharvest.io
--topology=private
--networking=weave
…….

18. Visibility IAMIngress SupportAutoscaling
Dashboard
Prometheus
Grafana
EFK
Stack
Heptio
Authenticator
Nginx
Ingress
Controller
External DNS
(Route 53)
Cluster
Autoscaler
Metrics Server
Cert Manager
(Let’s Encrypt)

19. 3. LIVE DEMO: KUBERNETES ON AWS

20. 4. CONTINUOUS DELIVERY ON KUBERNETES

21. NGINX Ingress Controller
Pod A (1)
container
Pod A (2)
container
Pod B (1)
container
Pod B (2)
container
Service A Service B
Ingress A Ingress B

22. docker:build helm:installhelm:push
Docker Registry
Docker
Image
Helm Repository
Helm
Chart
Kubernetes
Cluster
Pods
GitLab CI/CD pipeline

23. 5. LIVE DEMO: CI/CD ON KUBERNETES

24. Q & A