Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Kubernetes and Helm 101

8 views

Published on

My blog: http://zonov.me/
Slides to the Getting started workshop on Kubernetes. Performed together with with https://cloudlad.io/

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Kubernetes and Helm 101

  1. 1. K8S 101 “Open-source container-orchestration system”
  2. 2. OS level virtualization artifact. Environment isolation. Docker as an example. Containers
  3. 3. A group of computational instances working together.Cluster
  4. 4. Container orchestration tool. Tool for management, scaling and deployment of containerized apps. Designed by Google. Works with different containerization tools, including Docker. Kubernetes
  5. 5. Kubernetes Container orchestration tool. Tool for management, scaling and deployment of containerized apps. Designed by Google. Works with different containerization tools, including Docker. Pretty complex.
  6. 6. Node, Pod, Container
  7. 7. Node Pod Container
  8. 8. Deployment is a description of the cluster’s desired state. Manages rolling updates, self-healing and scaling. Service is an abstraction layer on top of the set of pods. Deployment, Service
  9. 9. ● Cluster ● Node ● Pod ● Container Keywords ● Deployment ● Service
  10. 10. Hands-on time! https://bit.ly/2BDaPl8
  11. 11. Helm “The package manager for Kubernetes”
  12. 12. Helm helps you manage Kubernetes applications Helm Charts helps you define, install, and upgrade even the most complex Kubernetes application. Charts are easy to create, version, share, and publish so start using Helm and stop the copy-and-paste. About
  13. 13. Helm and Tiller Helm Tiller
  14. 14. Helm The Helm Client is a command-line client for end users. The client is responsible for the following domains: Local chart development Managing repositories Interacting with the Tiller server Sending charts to be installed Asking for information about releases Requesting upgrading or uninstalling of existing releases
  15. 15. The Tiller Server is an in-cluster server that interacts with the Helm client, and interfaces with the Kubernetes API server. The server is responsible for the following: Listening for incoming requests from the Helm client Combining a chart and configuration to build a release Installing charts into Kubernetes, and then tracking the subsequent release Upgrading and uninstalling charts by interacting with Kubernetes In a nutshell, the client is responsible for managing charts, and the server is responsible for managing releases. Tiller
  16. 16. Facts Whenever you install a chart, a new release is created. So one chart can be installed multiple times into the same cluster. And each can be independently managed and upgraded. To uninstall a release, use the helm delete command: Because Helm tracks your releases even after you’ve deleted them, you can audit a cluster’s history, and even undelete a release (with helm rollback)
  17. 17. That is all

×