Triangle Kubernetes Meet Up #3 (June 9, 2016) From Beginner to Expert

Size: px

Start display at page:

Download "Triangle Kubernetes Meet Up #3 (June 9, 2016) From Beginner to Expert"

Clementine Webster
5 years ago
Views:

1 Triangle Kubernetes Meet Up #3 (June 9, 2016) From Beginner to Expert

Who We Are? System Integrator www.cloudperceptions.com blog.cloudperceptions.com Shixiong Shang Founder and CEO CloudPerceptions email: shshang@cloudperceptions.

2 Who We Are? System Integrator blog.cloudperceptions.com Shixiong Shang Founder and CEO CloudPerceptions CCIE R&S, SP Video OpenStack Vancouver/Austin Speaker Triangle Kubernete Meetup Organizer Randy Tuttle Co-Founder and CTO CloudPerceptions SP VoIP, SP Video OpenStack Austin Speaker Triangle Kubernete Meetup Organizer 2

3 A Few Things We have > 200 members now! Slack channel for this meet up community ( Session in July: July 28 in this building (not on 2nd Thursday) Ben from Red Hat, Ray from Google Future sessions: Kubernetes hands-on working shop (Ray) Openshift/Kubernetes as ideal platform for micro services deployment (Rafael) Topics about OpenShift operation (Matt) More from Google (Sandeep, etc.) Something you will like: Book from Grant Shipley: OpenShift for Developers published by O Reilly Kubernets stickers 3

4 Key Concepts (refresh your memory

5 #kubernetes

6 Key Concepts Container: You knew it already Pod: Co-located group of containers and volumes Service: Defines a set of pods and a means by which to access them (IP, DNS name) Volume: A directory which is accessible to a Container as part of its filesystem Label: K/V pair attached to a resource to convey a user-defined attribute Replication Controller: Ensures that a specified number of pod replicas are running at any one time Node: Physical or VM onto which pods can be scheduled

7 Architecture

8 Hello Kubernetes! * 8

9 Master Node: Kubernetes Control Plane api server etcd scheduler controller manager 9

10 Master Node: Kubernetes Control Plane etcd: persistent k/v store rich api and powerful client stores cluster level configuration and state information 10

11 Master Node: Kubernetes Control Plane api server: The most important component Handles CRUD operations The only entrance to etcd 11

12 Master Node: Kubernetes Control Plane scheduler: Positions Pod onto Node (i.e. binding) Three-stage process (predicates, priorities, choose) Pluggable 12

13 Master Node: Kubernetes Control Plane controller manager: A lot of controllers (replication controller, node controller, service controller, endpoint controller, namespace controller, serviceaccount controller, resource quota controller, etc.) 13

14 Worker Node (a.k.a. Minion Node) kubelet proxy cadvisor docker engine 14

15 Worker Node (a.k.a. Minion Node) kubelet: Maintains a set of pods on local node Works with pod specs Node agent 15

16 Worker Node (a.k.a. Minion Node) proxy: Support service and endpoints (via DNS) Implementation of cluster-ip A simple network proxy and load balancer Can do TCP/UDP stream forwarding 16

17 Worker Node (a.k.a. Minion Node) cadvisor: As part of kubelet Collects, aggregates, processes resource usage and performance info about running containers Exports by container and machine-wide 17

18 Next Steps Several Thoughts Networking (Flannel) Add-On Services (SkyDNS, Heapster, Fluentd) Cluster Installation and Configuration What topics interest you the most? 18

Kubernetes introduction. Container orchestration

Kubernetes introduction. Container orchestration Kubernetes introduction Container orchestration Container Orchestration Why we need container orchestration? Restart containers if they are not healthy. Provide private container network. Service discovery.