Download as PDF, PPTX
Uploaded byEduardo Garcia Moyano
Quick introduction to Kubernetes
1) Kubernetes is an open-source system for managing containerized applications and services across multiple hosts. It was created by Google in 2014 to automate deployment, scaling, and operations of application containers. 2) Kubernetes allows for automatic deployment and scaling of applications. It makes applications portable and lightweight by running them in containers. 3) The document provides an overview of key Kubernetes concepts including pods, replication controllers, and services. Pods are the smallest deployable units that can contain one or more containers which share resources. Replication controllers ensure a specified number of pod replicas are running. Services define a policy to access pods through labels.
More Related Content
Similar to Quick introduction to Kubernetes
Quick introduction to Kubernetes
- 1. “Introduction to kubernetes” EduGarcía Developer @godraude [email protected]
- 2. Table of Contents •Quick introduction to containers • What is Kubernetes? • Why Kubernetes? • General overview • Proof of concept
- 3. Quick intro tocontainers
- 4. Linux containers anddocker • Linux containers • Provides isolated namespaces • Runs on top of the system kernel • Less overhead than virtual machines • Docker • Provides an api to manage linux containers
- 5.
- 6. What is kubernetes? •A system for managing containerized applications across a cluster of nodes • Started by google in 2014 • Open-source project written in GO • Version 1.0 released July 2015 • Benefits • Automatic deployment • Scalable • Portable • Lightweight
- 8.
- 9.
- 10.
- 11.
- 12. Pods • A podis a collection of containers that run on a host. It’s the smallest unit in kubernetes. • It can be seeing as a virtualised host • Each pod has an IP address and full access to others computers or containers in the same network • It groups tightly coupled applications • They share PID namespace, network and hostname • They have access to shared volumes • Each application is a container itself • When a node dies, the scheduled pod dies with it
- 13. Pod definition It’s adefinition of a desired state. Kubernetes is in charge of having the current state as the desired state. Template example: apiVersion: v1 kind: Pod metadata: name: nginx labels: name: nginx spec: containers: - image: bitnami/nginx name: nginx ports: - containerPort: 80
- 14.
- 15. Replication Controller • ReplicationController • It ensures that a number of pod replicas are running • Creates new pods from a template apiVersion: v1 kind: ReplicationController metadata: name: nginx-controller spec: replicas: 2 selector: app: nginx template: metadata: labels: app: nginx spec: containers: - name: nginx image: bitnami/nginx ports: - containerPort: 80
- 16.
- 17. Services • Services • Definesa a policy to access a set of pods • If a pod goes down and a new one is created, it will still be accesible from the outside through its service • The set of pods to which a service applies are defined by a label
- 18. Defining a service apiVersion:v1 kind: Service metadata: labels: name: nginx name: nginx-service spec: ports: - port: 80 selector: name: nginx type: LoadBalancer
- 19. Interacting with thecluster Create a pod: List all pods: Delete pod by name: $ kubectl get pods $ kubectl create -f nginx.yaml $ kubectl delete pod nginx
- 20.
- 21.
- 22.
- 23.
- 24.