Container Orchestration using Kubernetes

Container Orchestration using Kubernetes

• 1.
  Hesham Amin http://heshamamin.com/ @heshamamin https://www.linkedin.com/in/heshamaamin/
• 2.
   Docker container= Process  Not a complete application (Usually) 2
• 3.
   Coordinate containersdeployment  Define relations between containers  Load Balancing  Service discovery  Scale  Rolling updates  Rollback  Management  Resource optimization 3
• 4.
   By Google Supported on GKE  Azure Container Service  Others (AWS / On-prem) 4
• 5.
  5
• 6.
  Node Master(s) Kubelet API Proxy Node Node Kubelet Azure load balancer Availability set
• 7.
   Collections ofnodes and other resources 7
• 8.
   Virtual orPhysical machines  Worker Node is a machine that hosts the containers  Master nodes: control workers  Created by the host and registered with Kubernetes 8
• 9.
   The smallestlogical unit of deployment  Collection of containers  Usually one  Share IP and port space (localhost)  Not durable 9
• 10.
  10 apiVersion: v1 kind: Pod metadata: name:pod-example labels: env: test spec: containers: - image: nginx name: nginx
• 11.
   Abstraction whichdefines a logical set of Pods and a policy by which to access them.  This set of Pods are determined using selectors. 11
• 12.
  12 kind: Service apiVersion: v1 metadata: #Unique key of the Service instance name: service-example spec: ports: # Accept traffic sent to port 80 - name: http port: 80 targetPort: 80 selector: # Loadbalance traffic across Pods matching # this label selector app: nginx # Create an HA proxy in the cloud provider # with an External IP address - *Only supported # by some cloud providers* type: LoadBalancer
• 13.
   Declarative desiredstate of Replica Sets  Support scaling and autoscaling  Can be rolled-back 13
• 14.
  14 apiVersion: extensions/v1beta1 kind: Deployment metadata: #Unique key of the Deployment instance name: deployment-example spec: # 3 Pods should exist at all times. replicas: 3 # Keep record of 2 revisions for rollback revisionHistoryLimit: 2 template: metadata: labels: # Apply this label to pods and default # the Deployment label selector to this value app: nginx spec: containers: -name: nginx # Run this image image: nginx:1.10
• 15.
   Ensure aspecified number of Pods is running at any time  Used for scaling 15
• 16.
   Group ofStateful Pods.  Stable, unique network identifiers.  Stable, persistent storage. 16
• 17.
   Scope fornames. Names of resources are unique within a namespace.  A way for managing resource quotas:  Number of objects  Memory  CPU Cores  Used for large clusters. 17
• 18.
  18