SlideShare a Scribd company logo

Digging into helm

Download as PPTX, PDF
상
상준 윤

Digging into helm

Engineering
1 of 51
Downloaded 34 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Digging into Helm 윤상준 2018.10 sj.yun@sk.com
Step Helm 개념 Helm 사용 Helm 개발 Helm 호스팅 Helm 운영
Helm?
Helm? “Helm is the best way to find, share, and use software built for Kubernetes” [https://helm.sh]
Helm ● Kubernetes를 위한 패키지 관리 툴 //Kubetnetes $ helm install stable/mysql //Homebrew $ brew install mysql //Apt $ apt-get install mysql-server //Yum $ yum install mysql-server
Chart ● Helm에서 애플리케이션 패키징을 하기 위해 사용하는 형식 ● Chart는 Kubernetes resource의 집합
Helm Features
//Helm $ helm install stable/mysql MySQL Server (Deployment) Persistent Volume (PVC) /etc/mysql/conf.d (Configmap) Password (Secret) Access Endpoint (Service) //Kubernetes yaml $ kubectl create -f deployment.yaml $ kubectl create -f svc.yaml $ kubectl create -f pvc.yaml $ kubectl create -f secret.yaml $ kubectl create -f configmap.yaml #1 Manage Complexity
#2 Easy Updates ● Upgrade 명령을 사용하여 설정이나 버전을 쉽게 업데이트 $ helm upgrade mysql-release stable/mysql --set mysqlRootPassword="password" $ helm upgrade mysql-release stable/mysql --version x.x.x
#3 Simple Sharing $ helm package demoPackage Share Download $ mv demo-0.1.0.tgz stable $ helm repo index stable --url https://example.github.io/my-charts/stable $ helm repo add my-charts https://example.github.io/my-charts $ helm install my-charts/demo
#4 Rollback ● Rollback 명령을 사용하여 이전 버전 또는 특정 버전으로 쉽게 복구 $ helm history REVISION UPDATED STATUS CHART DESCRIPTION 1 Thu Aug 15 00:49:37 2018 SUPERSEDED mysql-5.0.1 Install complete ... 10 Thu Aug 16 00:49:37 2018 DEPLOYED mysql-5.0.10 Upgrade complete $ helm rollback mysql [REVISION_NUMBER]
Helm 사용하기
5
#1 Search #2 Install #3 Upgrade #4 Rollback #5 Delete
#1 Search ● Helm을 최초 설치하면 Kubernetes official repository에 기본적으로 연동 $ helm repo list NAME URL stable https://kubernetes-charts.storage.googleapis.com local http://127.0.0.1:8879/charts $ helm search NAME CHART VERSION APP VERSION DESCRIPTION stable/wordpress 2.1.10 4.9.8 Web publishing platform for building... stable/jenkins 0.16.19 2.121.2 Open source continuous integration... stable/mariadb 4.3.3 10.1.35 Fast, reliable, scalable, and easy to... stable/mysql 0.8.3 5.7.14 Fast, reliable, scalable, and easy to... … $ helm search mysql NAME CHART VERSION APP VERSION DESCRIPTION stable/mysql 0.8.3 5.7.14 Fast, reliable, scalable, and easy... stable/mysqldump 0.1.0 5.7.21 A Helm chart to help backup... stable/mariadb 4.3.3 10.1.35 Fast, reliable, scalable, and easy...
#1 Search ● Inspect 명령으로 상세 정보 출력 $ helm inspect stable/mariadb appVersion: 10.1.35 description: Fast, reliable, scalable, and easy to use open-source relational database system. MariaDB Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. Highly available MariaDB cluster. engine: gotpl home: https://mariadb.org icon: https://bitnami.com/assets/stacks/mariadb/img/mariadb-stack-220x234.png keywords: - mariadb - mysql - database - sql - prometheus
#2 Install ● Install 명령으로 원하는 chart를 바로 설치 # helm install [REPO_NAME/CHART_NAME] --name [RELEASE_NAME] --namespace [NAMESPACE] $ helm install stable/mariadb NAME: willing-armadillo LAST DEPLOYED: Mon Oct 1 15:01:04 2018 NAMESPACE: default STATUS: DEPLOYED RESOURCES: ==> v1/Secret NAME TYPE DATA AGE willing-armadillo-mariadb Opaque 2 0s ==> v1/ConfigMap NAME DATA AGE willing-armadillo-mariadb-master-init-scripts 1 0s ... ==> v1/Service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE willing-armadillo-mariadb ClusterIP 10.3.255.79 <none> 3306/TCP 0s ... ==> v1beta1/StatefulSet NAME DESIRED CURRENT AGE willing-armadillo-mariadb-master 1 0 0s willing-armadillo-mariadb-slave 1 0 0s
#2 Install ● Notes에 애플리케이션을 사용하기 위한 가이드 출력 ... NOTES: Please be patient while the chart is being deployed Tip: Watch the deployment status using the command: kubectl get pods -w --namespace default -l release=willing-armadillo ... Administrator credentials: Username: root Password : $(kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root- password}" | base64 --decode) To connect to your database 1. Run a pod that you can use as a client: kubectl run willing-armadillo-mariadb-client --rm --tty -i --image docker.io/bitnami/mariadb:10.1.35-debian-9 -- namespace default --command -- bash 2. To connect to master service (read/write): mysql -h willing-armadillo-mariadb.default.svc.cluster.local -uroot -p my_database … $ kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -- decode JYHQDJY7Im
#3 Upgrade ● Upgrade 명령을 통해 설정이나 버전을 업데이트 $ helm list NAME REVISION UPDATED STATUS CHART NAMESPACE willing-armadillo 1 Mon Oct 1 15:01:04 2018 DEPLOYED mariadb-4.3.3 default $ helm upgrade willing-armadillo --set rootUser.password=”admin” stable/mariadb Release "willing-armadillo" has been upgraded. Happy Helming! LAST DEPLOYED: Mon Oct 1 15:42:55 2018 NAMESPACE: default STATUS: DEPLOYED … Administrator credentials: Username: root Password : $(kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root- password}" | base64 --decode) … $ kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 --decode ”admin”
#4 Rollback ● Rollback 명령을 사용하여 이전 버전 또는 특정 버전으로 쉽게 복구 $ helm list NAME REVISION UPDATED STATUS CHART NAMESPACE willing-armadillo 2 Mon Oct 1 15:42:55 2018 DEPLOYED mariadb-4.3.3 default $ helm history willing-armadillo REVISION UPDATED STATUS CHART DESCRIPTION 1 Mon Oct 1 15:01:04 2018 SUPERSEDED mariadb-4.3.3 Install complete 2 Mon Oct 1 15:42:55 2018 DEPLOYED mariadb-4.3.3 Upgrade complete $ helm rollback willing-armadillo 1 Rollback was a success! Happy Helming! $ helm history willing-armadillo REVISION UPDATED STATUS CHART DESCRIPTION 1 Mon Oct 1 15:01:04 2018 SUPERSEDED mariadb-4.3.3 Install complete 2 Mon Oct 1 15:42:55 2018 SUPERSEDED mariadb-4.3.3 Upgrade complete 3 Mon Oct 1 16:18:04 2018 DEPLOYED mariadb-4.3.3 Rollback to 1 $ kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -- decode JYHQDJY7Im
#5 Delete ● Delete 명령을 사용하여 설치된 Kubernetes 리소스 삭제 $ helm list NAME REVISION UPDATED STATUS CHART NAMESPACE willing-armadillo 2 Mon Oct 1 15:42:55 2018 DEPLOYED mariadb-4.3.3 default # “--purge” 옵션을 주면 release name 까지 삭제. 아니면 list에는 남아있음. $ helm del --purge willing-armadillo release "willing-armadillo" deleted # StatefulSet에서 “volumeClaimTemplates”을 통해 생성된 volume은 helm 삭제 후에도 남아있음. (make by design) # https://github.com/helm/charts/blob/master/stable/mariadb/templates/master-statefulset.yaml $ kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE data-w...-mariadb-master-0 Bound pvc-d24.. 8Gi RWO standard 1h data-w...-mariadb-slave-0 Bound pvc-d25.. 8Gi RWO standard 1h
[참고] Helm & Tiller 설치 ● Helm을 사용하기 위해서는 Tiller와 Helm Client를 설치 필요 ○ Tiller : Helm의 서버로 일반적으로 Kubernetes cluster에 설치 ○ Helm client : Helm 명령어를 실행하기 위한 CLI ● 설치 방법은 아래 블로그 참고 ○ https://yunsangjun.github.io/blog/helm/2018/05/27/installing-helm.html
Helm Chart 만들기
Helm chart 생성 및 구조 #1 ● Create 명령으로 Helm chart sample 생성 # helm create [CHART_NAME] $ helm create demo Creating demo demo/ .helmignore # 형상관리에서 제외할 파일이나 디렉토리 목록 Chart.yaml # Chart의 정보를 저장 charts # 이 chart에서 의존성을 가지고 있는 chart가 위치 templates # Kubernetes 리소스의 템플릿 파일(deployment, service, ingress 등의 yaml) values.yaml # 이 helm chart의 기본 설정 값을 저장. templates yaml 파일에서 사용 ● Sample chart 구조
Helm chart 생성 및 구조 #2 ● values.yaml 과 templates 구조 $ cat values.yaml replicaCount: 1 image: repository: nginx tag: stable pullPolicy: IfNotPresent nameOverride: "" fullnameOverride: "" service: type: ClusterIP port: 80 ingress: enabled: false ... $ cat templates/service.yaml apiVersion: v1 kind: Service metadata: name: {{ include "demo.fullname" . }} labels: app.kubernetes.io/name: {{ include "demo.name" . }} helm.sh/chart: {{ include "demo.chart" . }} app.kubernetes.io/instance: {{ .Release.Name }} app.kubernetes.io/managed-by: {{ .Release.Service }} spec: type: {{ .Values.service.type }} ports: - port: {{ .Values.service.port }} targetPort: http protocol: TCP name: http selector: app.kubernetes.io/name: {{ include "demo.name" . }} app.kubernetes.io/instance: {{ .Release.Name }}
Helm chart validation ● Lint 명령으로 Helm chart의 문법적인 오류 체크 $ helm lint demo ==> Linting ./ [INFO] Chart.yaml: icon is recommended [ERROR] templates/: render error in "demo/templates/deployment.yaml": template: demo/templates/deployment.yaml:11:22: executing "demo/templates/deployment.yaml" at <.Values.replica.coun...>: can't evaluate field count in type interface {} Error: 1 chart(s) linted, 1 chart(s) failed $ cat demo/templates/deployment.yaml ... spec: replicas: {{ .Values.replica.count }} => .Values.replicaCount로 수정 필요 $ cat demo/values.yaml ... replicaCount: 1
Helm chart package ● Package 명령으로 Helm chart package $ ls -all total 3 drwxr-xr-x 7 sangjunyun staff 224 10 3 15:56 . drwxr-xr-x 41 sangjunyun staff 1312 10 3 11:49 .. drwxr-xr-x 7 sangjunyun staff 224 10 3 12:01 demo $ helm package demo Successfully packaged chart and saved it to: PATH/demo-0.1.0.tgz $ ls -all total 3 drwxr-xr-x 7 sangjunyun staff 224 10 3 15:56 . drwxr-xr-x 41 sangjunyun staff 1312 10 3 11:49 .. drwxr-xr-x 7 sangjunyun staff 224 10 3 12:01 demo -rw-r--r-- 1 sangjunyun staff 2608 10 3 12:01 demo-0.1.0.tgz
Helm chart template ● Template 명령으로 Kubernetes 리소스 파일이 어떻게 생성될 지 미리 확인 $ helm template demo > output.yaml $ cat output.yaml --- # Source: demo/templates/service.yaml apiVersion: v1 kind: Service metadata: name: RELEASE-NAME-demo .. --- # Source: demo/templates/deployment.yaml apiVersion: apps/v1beta2 kind: Deployment metadata: name: RELEASE-NAME-demo ...
Helm chart simulate ● Install 명령에 “--dry-run --debug” 옵션을 붙여 Helm install 시뮬레이션 $ helm install demo --dry-run --debug ... NAME: lame-sasquatch … --- # Source: demo/templates/service.yaml apiVersion: v1 kind: Service metadata: name: lame-sasquatch-demo … --- # Source: demo/templates/deployment.yaml apiVersion: apps/v1beta2 kind: Deployment metadata: name: lame-sasquatch-demo …
Helm Chart 호스팅하기
Helm chart repository ● 내가 만든 Helm chart를 다른 사용자에게 공유하기 위해서는 Helm repository 가 필요 ● Official repository(https://github.com/helm/charts)에 Contribution하는 방법과 자체 repository를 사용하는 두 가지 방식 있음 ● 자체 repository는 크게 3가지 형태로 지원(웹 서버 기능 필요) ○ Github Pages ○ Object Storage(GCS, AWS S3, ICOS 등) ○ Ordinary Web Servers(Nginx, Apache)
Helm chart repository with Github Pages #1 ● 쉽고 무료로 사용할 수 있는 방법 ● Github Pages는 웹 서버 기능을 지원함 1. Github에 Repository 생성(여기서는 my-charts라고 가정) 2. Github Page 설정 Repository -> Settings -> Github Pages > Source > master branch 선택 > Save 선택 (설정 완료 후 나타나는 https://example.github.io/my-charts/ 주소가 웹 서버 주소
Helm chart repository with Github Pages #2 3. git repository checkout 및 stable 디렉토리 생성 $ git checkout https://github.com/example/my-charts.git $ cd my-charts & mkdir stable 4. helm 파일을 stable 디렉토리에 복사(앞에서 생성한 demo-0.1.0.tgz 사용) $ mv FILE_PATH/demo-0.1.0.tgz stable 5. Index 파일 생성. stable 디렉토리 하위에 index.yaml 파일 생성됨 # helm repo index [INDEX_FILE_PATH] --url [CHART_REPO_URL] $ helm repo index stable --url https://example.github.io/my-charts/stable 6. 변경사항 git에 commit $ git add --all & git commit -m 'init' & git push origin master 7. Chart repository 주소에 접속해 index 파일 확인 https://example.github.io/my-charts/stable/index.yaml
Helm chart repository with Github Pages #3 apiVersion: v1 entries: demo: - apiVersion: v1 appVersion: "1.0" created: 2018-10-03T12:14:26.693334507+09:00 description: A Helm chart for Kubernetes digest: c677efc778b455ad3b9d53c03d37cf0002d067ac80da35d0921672a77f3c9bc3 name: demo urls: - https://example.github.io/my-charts/stable/demo-0.1.0.tgz version: 0.1.0 generated: 2018-10-03T12:14:26.690034532+09:00 8. Index 파일의 helm chart 패키지 다운로드 확인 https://example.github.io/my-charts/stable/demo-0.1.0.tgz [참고] 샘플 helm repository https://github.com/YunSangJun/my-charts
Helm chart 공유 및 사용 #1 ● 준비된 helm chart와 repository를 다른 사용자들이 추가 및 사용 1. helm repository 추가 # helm repo add [REPO_NAME] [REPO_URL] $ helm repo add my-charts https://example.github.io/my-charts/stable 2. 추가한 repository 확인 $ help repo list NAME URL ... my-charts https://example.github.io/my-charts/stable 3. repository에서 chart 검색 $ helm search my-charts NAME CHART VERSION APP VERSION DESCRIPTION my-charts/demo 0.1.0 1.0 A Helm chart for Kubernetes
Helm chart 공유 및 사용 #2 4. chart 사용하기 $ helm install my-charts/demo NAME: flippant-narwhal LAST DEPLOYED: Wed Oct 3 15:11:52 2018 NAMESPACE: default STATUS: DEPLOYED RESOURCES: ==> v1beta2/Deployment NAME AGE flippant-narwhal-demo 0s … NOTES: 1. Get the application URL by running these commands: export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=demo,app.kubernetes.io/instance=flippant-narwhal" -o jsonpath="{.items[0].metadata.name}") echo "Visit http://127.0.0.1:8080 to use your application" kubectl port-forward $POD_NAME 8080:80
현실에서의 고민
Multi Cloud & Cluster? ● Kubernetes로 만든 애플리케이션 어떻게 Multi Cloud & Cluster에 배포? $ cat pvc.yaml kind: PersistentVolumeClaim spec: storageClassName: [???] storageClassName: gp2 storageClassName: ibm-file-bronze storageClassName: standard storageClassName: default
Kubernetes? ● Kubernetes 에서는 변수 치환 기능을 제공할 계획 없음. (make by design) https://github.com/kubernetes/kubernetes/issues/52787
Helming! ● Helm $ export STORAGE_CLASS = gp2 | ibm-file-bronze | standard | azurefile $ helm install stable/mariadb --set master.persistence.storageClass="${STORAGE_CLASS}"
Spinnaker + Helm ● Spinnaker의 Helm bake 기능을 활용과 연계 https://www.spinnaker.io/guides/user/kubernetes-v2/deploy-helm/
Monocular + Helm ● Monocular와 Helm repository를 연계해 앱 마켓플레이스 활용 https://github.com/helm/monocular
Helm 사용하기 고급
Chart의 설정 변경 #1 매개변수 사용 ● Chart source repository 문서의 설정 정보를 참고하여 설정 변경 $ helm install stable/mariadb --set image.tag=x.x.x https://github.com/helm/charts/tree/master/stable/mariadb
Chart의 설정 변경 #2 파일 사용 ● yaml file 형태로 설정 변경도 가능. Chart의 values.yaml의 형식을 참고해서 작 성 $ cat values.yaml image: tag: x.x.x ... $ helm install stable/mariadb -f values.yaml
Contribution
Helm chart contribution ● 내가 만든 애플리케이션을 kubernetes helm repository에 배포하고 싶다면?
Tips for contribution 1. Kubernetes helm code repository fork 2. 아래 가이드 참고하여 contributor 서명 후 commit a. https://github.com/helm/charts/blob/master/CONTRIBUTING.md 3. “helm create”로 만들어진 최신 버전 chart를 참고하여 내가 만든 chart 검토 4. Guidelines을 참고하여 내가 만든 chart 검토 a. https://github.com/helm/charts/blob/master/REVIEW_GUIDELINES.md 5. 내가 만든 chart를 incubator 디렉토리에 commit 6. Pull request!
참고자료 Helm 참고 자료 ● 블로그 : https://yunsangjun.github.io/blog/ Kubernetes 참고 자료 ● 블로그 : http://tech.cloudz-labs.io/
Q & A
감사합니다

More Related Content

PDF
Kubernetes & helm 활용
SK Telecom
 
PDF
helm 입문
choi sungwook
 
PPTX
Helm @ Orchestructure
Matthew Farina
 
PDF
Kubernetes Helm (Boulder Kubernetes Meetup, June 2016)
Matt Butcher
 
PPTX
Steering the Course with Helm
Dirk Jablonski
 
PPTX
Terraform
Phil Wilkins
 
PDF
Kubeflow Pipelines (with Tekton)
Animesh Singh
 
PDF
Helm – The package manager for Kubernetes
FabianRosenthal1
 
Kubernetes & helm 활용
SK Telecom
 
helm 입문
choi sungwook
 
Helm @ Orchestructure
Matthew Farina
 
Kubernetes Helm (Boulder Kubernetes Meetup, June 2016)
Matt Butcher
 
Steering the Course with Helm
Dirk Jablonski
 
Terraform
Phil Wilkins
 
Kubeflow Pipelines (with Tekton)
Animesh Singh
 
Helm – The package manager for Kubernetes
FabianRosenthal1
 

What's hot (20)

PDF
ssh-agentのすすめ
Masahiro NAKAYAMA
 
PPTX
React + Redux Introduction
Nikolaus Graf
 
PPTX
Introduction to git and github
Aderemi Dadepo
 
PPTX
Helm.pptx
SISTechnologies
 
PPTX
Introduction to helm
Jeeva Chelladhurai
 
PDF
Helm intro
Haggai Philip Zagury
 
PDF
Autoscaling Kubernetes
craigbox
 
PDF
Infrastructure as Code with Terraform and Ansible
DevOps Meetup Bern
 
PDF
Introduction to Git and GitHub
Vikram SV
 
PPTX
Kubernetes #6 advanced scheduling
Terry Cho
 
PPTX
Autoscaling in Kubernetes
Hrishikesh Deodhar
 
PDF
오픈소스로 만드는 DB 모니터링 시스템 (w/graphite+grafana)
I Goo Lee
 
PDF
Intro to Terraform
Josh Michielsen
 
PPTX
Introduction to github slideshare
Rakesh Sukumar
 
PDF
Helm - Application deployment management for Kubernetes
Alexei Ledenev
 
PDF
PostGIS 시작하기
Byeong-Hyeok Yu
 
PPTX
Final terraform
Gourav Varma
 
PDF
Hands-On Introduction to Kubernetes at LISA17
Ryan Jarvinen
 
PDF
Nestjs MasterClass Slides
Nir Kaufman
 
PPTX
[135] 오픈소스 데이터베이스, 은행 서비스에 첫발을 내밀다.
NAVER D2
 
ssh-agentのすすめ
Masahiro NAKAYAMA
 
React + Redux Introduction
Nikolaus Graf
 
Introduction to git and github
Aderemi Dadepo
 
Helm.pptx
SISTechnologies
 
Introduction to helm
Jeeva Chelladhurai
 
Helm intro
Haggai Philip Zagury
 
Autoscaling Kubernetes
craigbox
 
Infrastructure as Code with Terraform and Ansible
DevOps Meetup Bern
 
Introduction to Git and GitHub
Vikram SV
 
Kubernetes #6 advanced scheduling
Terry Cho
 
Autoscaling in Kubernetes
Hrishikesh Deodhar
 
오픈소스로 만드는 DB 모니터링 시스템 (w/graphite+grafana)
I Goo Lee
 
Intro to Terraform
Josh Michielsen
 
Introduction to github slideshare
Rakesh Sukumar
 
Helm - Application deployment management for Kubernetes
Alexei Ledenev
 
PostGIS 시작하기
Byeong-Hyeok Yu
 
Final terraform
Gourav Varma
 
Hands-On Introduction to Kubernetes at LISA17
Ryan Jarvinen
 
Nestjs MasterClass Slides
Nir Kaufman
 
[135] 오픈소스 데이터베이스, 은행 서비스에 첫발을 내밀다.
NAVER D2
 
Ad

Similar to Digging into helm (20)

PDF
XECon2015 :: [1-5] 김훈민 - 서버 운영자가 꼭 알아야 할 Docker
XpressEngine
 
PDF
Docker at Deview 2013
Jude Kim
 
PDF
AWS Kubernetes 서비스 자세히 살펴보기 (정영준 & 이창수, AWS 솔루션즈 아키텍트) :: AWS DevDay2018
Amazon Web Services Korea
 
PDF
Docker at Deview 2013
Jude Kim
 
PDF
[GitOps] Argo CD on GKE (v0.9.2).pdf
Jo Hoon
 
PPTX
BRK3713 - Microsoft Azure에서 Windows와 Linux를 동시에 사용하는 하이브리드 Kubernetes 클러스터 구축
Jung Hyun Nam
 
PDF
왜 쿠버네티스는 systemd로 cgroup을 관리하려고 할까요
Jo Hoon
 
PDF
Kubernetes on Premise Practical Guide
Chan Shik Lim
 
PDF
[오픈소스컨설팅]쿠버네티스를 활용한 개발환경 구축
Ji-Woong Choi
 
PDF
Dockerfile과 Bash
pyrasis
 
PDF
백억개의 로그를 모아 검색하고 분석하고 학습도 시켜보자 : 로기스
NAVER D2
 
PDF
decapod cncg seoul 2020
Esther Kim
 
PDF
Docker로 서버 개발 편하게 하기
Dronix
 
PDF
Kubernetes on Premise
Chan Shik Lim
 
PDF
K8s in action02
Sunggon Song
 
PPTX
IoT with Raspberry Pi + Node JS - Chapter 1
Park Jonggun
 
PDF
Kubernetes in action
Bingu Shim
 
PPTX
[AWSKRUG 컨테이너 소모임] Rancher 기본 입문
Hyunmin Kim
 
PDF
쿠알못이 Amazon EKS로 안정적인 서비스 운영하기 - 최용호(넥슨코리아) :: AWS Community Day 2020
AWSKRUG - AWS한국사용자모임
 
PDF
Prometheus in openstack-helm
성일 임
 
XECon2015 :: [1-5] 김훈민 - 서버 운영자가 꼭 알아야 할 Docker
XpressEngine
 
Docker at Deview 2013
Jude Kim
 
AWS Kubernetes 서비스 자세히 살펴보기 (정영준 & 이창수, AWS 솔루션즈 아키텍트) :: AWS DevDay2018
Amazon Web Services Korea
 
Docker at Deview 2013
Jude Kim
 
[GitOps] Argo CD on GKE (v0.9.2).pdf
Jo Hoon
 
BRK3713 - Microsoft Azure에서 Windows와 Linux를 동시에 사용하는 하이브리드 Kubernetes 클러스터 구축
Jung Hyun Nam
 
왜 쿠버네티스는 systemd로 cgroup을 관리하려고 할까요
Jo Hoon
 
Kubernetes on Premise Practical Guide
Chan Shik Lim
 
[오픈소스컨설팅]쿠버네티스를 활용한 개발환경 구축
Ji-Woong Choi
 
Dockerfile과 Bash
pyrasis
 
백억개의 로그를 모아 검색하고 분석하고 학습도 시켜보자 : 로기스
NAVER D2
 
decapod cncg seoul 2020
Esther Kim
 
Docker로 서버 개발 편하게 하기
Dronix
 
Kubernetes on Premise
Chan Shik Lim
 
K8s in action02
Sunggon Song
 
IoT with Raspberry Pi + Node JS - Chapter 1
Park Jonggun
 
Kubernetes in action
Bingu Shim
 
[AWSKRUG 컨테이너 소모임] Rancher 기본 입문
Hyunmin Kim
 
쿠알못이 Amazon EKS로 안정적인 서비스 운영하기 - 최용호(넥슨코리아) :: AWS Community Day 2020
AWSKRUG - AWS한국사용자모임
 
Prometheus in openstack-helm
성일 임
 
Ad

Digging into helm

  • 2. Step Helm 개념 Helm 사용 Helm 개발 Helm 호스팅 Helm 운영
  • 4. Helm? “Helm is the best way to find, share, and use software built for Kubernetes” [https://helm.sh]
  • 5. Helm ● Kubernetes를 위한 패키지 관리 툴 //Kubetnetes $ helm install stable/mysql //Homebrew $ brew install mysql //Apt $ apt-get install mysql-server //Yum $ yum install mysql-server
  • 6. Chart ● Helm에서 애플리케이션 패키징을 하기 위해 사용하는 형식 ● Chart는 Kubernetes resource의 집합
  • 8. //Helm $ helm install stable/mysql MySQL Server (Deployment) Persistent Volume (PVC) /etc/mysql/conf.d (Configmap) Password (Secret) Access Endpoint (Service) //Kubernetes yaml $ kubectl create -f deployment.yaml $ kubectl create -f svc.yaml $ kubectl create -f pvc.yaml $ kubectl create -f secret.yaml $ kubectl create -f configmap.yaml #1 Manage Complexity
  • 9. #2 Easy Updates ● Upgrade 명령을 사용하여 설정이나 버전을 쉽게 업데이트 $ helm upgrade mysql-release stable/mysql --set mysqlRootPassword="password" $ helm upgrade mysql-release stable/mysql --version x.x.x
  • 10. #3 Simple Sharing $ helm package demoPackage Share Download $ mv demo-0.1.0.tgz stable $ helm repo index stable --url https://example.github.io/my-charts/stable $ helm repo add my-charts https://example.github.io/my-charts $ helm install my-charts/demo
  • 11. #4 Rollback ● Rollback 명령을 사용하여 이전 버전 또는 특정 버전으로 쉽게 복구 $ helm history REVISION UPDATED STATUS CHART DESCRIPTION 1 Thu Aug 15 00:49:37 2018 SUPERSEDED mysql-5.0.1 Install complete ... 10 Thu Aug 16 00:49:37 2018 DEPLOYED mysql-5.0.10 Upgrade complete $ helm rollback mysql [REVISION_NUMBER]
  • 13. 5
  • 14. #1 Search #2 Install #3 Upgrade #4 Rollback #5 Delete
  • 15. #1 Search ● Helm을 최초 설치하면 Kubernetes official repository에 기본적으로 연동 $ helm repo list NAME URL stable https://kubernetes-charts.storage.googleapis.com local http://127.0.0.1:8879/charts $ helm search NAME CHART VERSION APP VERSION DESCRIPTION stable/wordpress 2.1.10 4.9.8 Web publishing platform for building... stable/jenkins 0.16.19 2.121.2 Open source continuous integration... stable/mariadb 4.3.3 10.1.35 Fast, reliable, scalable, and easy to... stable/mysql 0.8.3 5.7.14 Fast, reliable, scalable, and easy to... … $ helm search mysql NAME CHART VERSION APP VERSION DESCRIPTION stable/mysql 0.8.3 5.7.14 Fast, reliable, scalable, and easy... stable/mysqldump 0.1.0 5.7.21 A Helm chart to help backup... stable/mariadb 4.3.3 10.1.35 Fast, reliable, scalable, and easy...
  • 16. #1 Search ● Inspect 명령으로 상세 정보 출력 $ helm inspect stable/mariadb appVersion: 10.1.35 description: Fast, reliable, scalable, and easy to use open-source relational database system. MariaDB Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. Highly available MariaDB cluster. engine: gotpl home: https://mariadb.org icon: https://bitnami.com/assets/stacks/mariadb/img/mariadb-stack-220x234.png keywords: - mariadb - mysql - database - sql - prometheus
  • 17. #2 Install ● Install 명령으로 원하는 chart를 바로 설치 # helm install [REPO_NAME/CHART_NAME] --name [RELEASE_NAME] --namespace [NAMESPACE] $ helm install stable/mariadb NAME: willing-armadillo LAST DEPLOYED: Mon Oct 1 15:01:04 2018 NAMESPACE: default STATUS: DEPLOYED RESOURCES: ==> v1/Secret NAME TYPE DATA AGE willing-armadillo-mariadb Opaque 2 0s ==> v1/ConfigMap NAME DATA AGE willing-armadillo-mariadb-master-init-scripts 1 0s ... ==> v1/Service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE willing-armadillo-mariadb ClusterIP 10.3.255.79 <none> 3306/TCP 0s ... ==> v1beta1/StatefulSet NAME DESIRED CURRENT AGE willing-armadillo-mariadb-master 1 0 0s willing-armadillo-mariadb-slave 1 0 0s
  • 18. #2 Install ● Notes에 애플리케이션을 사용하기 위한 가이드 출력 ... NOTES: Please be patient while the chart is being deployed Tip: Watch the deployment status using the command: kubectl get pods -w --namespace default -l release=willing-armadillo ... Administrator credentials: Username: root Password : $(kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root- password}" | base64 --decode) To connect to your database 1. Run a pod that you can use as a client: kubectl run willing-armadillo-mariadb-client --rm --tty -i --image docker.io/bitnami/mariadb:10.1.35-debian-9 -- namespace default --command -- bash 2. To connect to master service (read/write): mysql -h willing-armadillo-mariadb.default.svc.cluster.local -uroot -p my_database … $ kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -- decode JYHQDJY7Im
  • 19. #3 Upgrade ● Upgrade 명령을 통해 설정이나 버전을 업데이트 $ helm list NAME REVISION UPDATED STATUS CHART NAMESPACE willing-armadillo 1 Mon Oct 1 15:01:04 2018 DEPLOYED mariadb-4.3.3 default $ helm upgrade willing-armadillo --set rootUser.password=”admin” stable/mariadb Release "willing-armadillo" has been upgraded. Happy Helming! LAST DEPLOYED: Mon Oct 1 15:42:55 2018 NAMESPACE: default STATUS: DEPLOYED … Administrator credentials: Username: root Password : $(kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root- password}" | base64 --decode) … $ kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 --decode ”admin”
  • 20. #4 Rollback ● Rollback 명령을 사용하여 이전 버전 또는 특정 버전으로 쉽게 복구 $ helm list NAME REVISION UPDATED STATUS CHART NAMESPACE willing-armadillo 2 Mon Oct 1 15:42:55 2018 DEPLOYED mariadb-4.3.3 default $ helm history willing-armadillo REVISION UPDATED STATUS CHART DESCRIPTION 1 Mon Oct 1 15:01:04 2018 SUPERSEDED mariadb-4.3.3 Install complete 2 Mon Oct 1 15:42:55 2018 DEPLOYED mariadb-4.3.3 Upgrade complete $ helm rollback willing-armadillo 1 Rollback was a success! Happy Helming! $ helm history willing-armadillo REVISION UPDATED STATUS CHART DESCRIPTION 1 Mon Oct 1 15:01:04 2018 SUPERSEDED mariadb-4.3.3 Install complete 2 Mon Oct 1 15:42:55 2018 SUPERSEDED mariadb-4.3.3 Upgrade complete 3 Mon Oct 1 16:18:04 2018 DEPLOYED mariadb-4.3.3 Rollback to 1 $ kubectl get secret --namespace default willing-armadillo-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -- decode JYHQDJY7Im
  • 21. #5 Delete ● Delete 명령을 사용하여 설치된 Kubernetes 리소스 삭제 $ helm list NAME REVISION UPDATED STATUS CHART NAMESPACE willing-armadillo 2 Mon Oct 1 15:42:55 2018 DEPLOYED mariadb-4.3.3 default # “--purge” 옵션을 주면 release name 까지 삭제. 아니면 list에는 남아있음. $ helm del --purge willing-armadillo release "willing-armadillo" deleted # StatefulSet에서 “volumeClaimTemplates”을 통해 생성된 volume은 helm 삭제 후에도 남아있음. (make by design) # https://github.com/helm/charts/blob/master/stable/mariadb/templates/master-statefulset.yaml $ kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE data-w...-mariadb-master-0 Bound pvc-d24.. 8Gi RWO standard 1h data-w...-mariadb-slave-0 Bound pvc-d25.. 8Gi RWO standard 1h
  • 22. [참고] Helm & Tiller 설치 ● Helm을 사용하기 위해서는 Tiller와 Helm Client를 설치 필요 ○ Tiller : Helm의 서버로 일반적으로 Kubernetes cluster에 설치 ○ Helm client : Helm 명령어를 실행하기 위한 CLI ● 설치 방법은 아래 블로그 참고 ○ https://yunsangjun.github.io/blog/helm/2018/05/27/installing-helm.html
  • 24. Helm chart 생성 및 구조 #1 ● Create 명령으로 Helm chart sample 생성 # helm create [CHART_NAME] $ helm create demo Creating demo demo/ .helmignore # 형상관리에서 제외할 파일이나 디렉토리 목록 Chart.yaml # Chart의 정보를 저장 charts # 이 chart에서 의존성을 가지고 있는 chart가 위치 templates # Kubernetes 리소스의 템플릿 파일(deployment, service, ingress 등의 yaml) values.yaml # 이 helm chart의 기본 설정 값을 저장. templates yaml 파일에서 사용 ● Sample chart 구조
  • 25. Helm chart 생성 및 구조 #2 ● values.yaml 과 templates 구조 $ cat values.yaml replicaCount: 1 image: repository: nginx tag: stable pullPolicy: IfNotPresent nameOverride: "" fullnameOverride: "" service: type: ClusterIP port: 80 ingress: enabled: false ... $ cat templates/service.yaml apiVersion: v1 kind: Service metadata: name: {{ include "demo.fullname" . }} labels: app.kubernetes.io/name: {{ include "demo.name" . }} helm.sh/chart: {{ include "demo.chart" . }} app.kubernetes.io/instance: {{ .Release.Name }} app.kubernetes.io/managed-by: {{ .Release.Service }} spec: type: {{ .Values.service.type }} ports: - port: {{ .Values.service.port }} targetPort: http protocol: TCP name: http selector: app.kubernetes.io/name: {{ include "demo.name" . }} app.kubernetes.io/instance: {{ .Release.Name }}
  • 26. Helm chart validation ● Lint 명령으로 Helm chart의 문법적인 오류 체크 $ helm lint demo ==> Linting ./ [INFO] Chart.yaml: icon is recommended [ERROR] templates/: render error in "demo/templates/deployment.yaml": template: demo/templates/deployment.yaml:11:22: executing "demo/templates/deployment.yaml" at <.Values.replica.coun...>: can't evaluate field count in type interface {} Error: 1 chart(s) linted, 1 chart(s) failed $ cat demo/templates/deployment.yaml ... spec: replicas: {{ .Values.replica.count }} => .Values.replicaCount로 수정 필요 $ cat demo/values.yaml ... replicaCount: 1
  • 27. Helm chart package ● Package 명령으로 Helm chart package $ ls -all total 3 drwxr-xr-x 7 sangjunyun staff 224 10 3 15:56 . drwxr-xr-x 41 sangjunyun staff 1312 10 3 11:49 .. drwxr-xr-x 7 sangjunyun staff 224 10 3 12:01 demo $ helm package demo Successfully packaged chart and saved it to: PATH/demo-0.1.0.tgz $ ls -all total 3 drwxr-xr-x 7 sangjunyun staff 224 10 3 15:56 . drwxr-xr-x 41 sangjunyun staff 1312 10 3 11:49 .. drwxr-xr-x 7 sangjunyun staff 224 10 3 12:01 demo -rw-r--r-- 1 sangjunyun staff 2608 10 3 12:01 demo-0.1.0.tgz
  • 28. Helm chart template ● Template 명령으로 Kubernetes 리소스 파일이 어떻게 생성될 지 미리 확인 $ helm template demo > output.yaml $ cat output.yaml --- # Source: demo/templates/service.yaml apiVersion: v1 kind: Service metadata: name: RELEASE-NAME-demo .. --- # Source: demo/templates/deployment.yaml apiVersion: apps/v1beta2 kind: Deployment metadata: name: RELEASE-NAME-demo ...
  • 29. Helm chart simulate ● Install 명령에 “--dry-run --debug” 옵션을 붙여 Helm install 시뮬레이션 $ helm install demo --dry-run --debug ... NAME: lame-sasquatch … --- # Source: demo/templates/service.yaml apiVersion: v1 kind: Service metadata: name: lame-sasquatch-demo … --- # Source: demo/templates/deployment.yaml apiVersion: apps/v1beta2 kind: Deployment metadata: name: lame-sasquatch-demo …
  • 31. Helm chart repository ● 내가 만든 Helm chart를 다른 사용자에게 공유하기 위해서는 Helm repository 가 필요 ● Official repository(https://github.com/helm/charts)에 Contribution하는 방법과 자체 repository를 사용하는 두 가지 방식 있음 ● 자체 repository는 크게 3가지 형태로 지원(웹 서버 기능 필요) ○ Github Pages ○ Object Storage(GCS, AWS S3, ICOS 등) ○ Ordinary Web Servers(Nginx, Apache)
  • 32. Helm chart repository with Github Pages #1 ● 쉽고 무료로 사용할 수 있는 방법 ● Github Pages는 웹 서버 기능을 지원함 1. Github에 Repository 생성(여기서는 my-charts라고 가정) 2. Github Page 설정 Repository -> Settings -> Github Pages > Source > master branch 선택 > Save 선택 (설정 완료 후 나타나는 https://example.github.io/my-charts/ 주소가 웹 서버 주소
  • 33. Helm chart repository with Github Pages #2 3. git repository checkout 및 stable 디렉토리 생성 $ git checkout https://github.com/example/my-charts.git $ cd my-charts & mkdir stable 4. helm 파일을 stable 디렉토리에 복사(앞에서 생성한 demo-0.1.0.tgz 사용) $ mv FILE_PATH/demo-0.1.0.tgz stable 5. Index 파일 생성. stable 디렉토리 하위에 index.yaml 파일 생성됨 # helm repo index [INDEX_FILE_PATH] --url [CHART_REPO_URL] $ helm repo index stable --url https://example.github.io/my-charts/stable 6. 변경사항 git에 commit $ git add --all & git commit -m 'init' & git push origin master 7. Chart repository 주소에 접속해 index 파일 확인 https://example.github.io/my-charts/stable/index.yaml
  • 34. Helm chart repository with Github Pages #3 apiVersion: v1 entries: demo: - apiVersion: v1 appVersion: "1.0" created: 2018-10-03T12:14:26.693334507+09:00 description: A Helm chart for Kubernetes digest: c677efc778b455ad3b9d53c03d37cf0002d067ac80da35d0921672a77f3c9bc3 name: demo urls: - https://example.github.io/my-charts/stable/demo-0.1.0.tgz version: 0.1.0 generated: 2018-10-03T12:14:26.690034532+09:00 8. Index 파일의 helm chart 패키지 다운로드 확인 https://example.github.io/my-charts/stable/demo-0.1.0.tgz [참고] 샘플 helm repository https://github.com/YunSangJun/my-charts
  • 35. Helm chart 공유 및 사용 #1 ● 준비된 helm chart와 repository를 다른 사용자들이 추가 및 사용 1. helm repository 추가 # helm repo add [REPO_NAME] [REPO_URL] $ helm repo add my-charts https://example.github.io/my-charts/stable 2. 추가한 repository 확인 $ help repo list NAME URL ... my-charts https://example.github.io/my-charts/stable 3. repository에서 chart 검색 $ helm search my-charts NAME CHART VERSION APP VERSION DESCRIPTION my-charts/demo 0.1.0 1.0 A Helm chart for Kubernetes
  • 36. Helm chart 공유 및 사용 #2 4. chart 사용하기 $ helm install my-charts/demo NAME: flippant-narwhal LAST DEPLOYED: Wed Oct 3 15:11:52 2018 NAMESPACE: default STATUS: DEPLOYED RESOURCES: ==> v1beta2/Deployment NAME AGE flippant-narwhal-demo 0s … NOTES: 1. Get the application URL by running these commands: export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=demo,app.kubernetes.io/instance=flippant-narwhal" -o jsonpath="{.items[0].metadata.name}") echo "Visit http://127.0.0.1:8080 to use your application" kubectl port-forward $POD_NAME 8080:80
  • 38. Multi Cloud & Cluster? ● Kubernetes로 만든 애플리케이션 어떻게 Multi Cloud & Cluster에 배포? $ cat pvc.yaml kind: PersistentVolumeClaim spec: storageClassName: [???] storageClassName: gp2 storageClassName: ibm-file-bronze storageClassName: standard storageClassName: default
  • 39. Kubernetes? ● Kubernetes 에서는 변수 치환 기능을 제공할 계획 없음. (make by design) https://github.com/kubernetes/kubernetes/issues/52787
  • 40. Helming! ● Helm $ export STORAGE_CLASS = gp2 | ibm-file-bronze | standard | azurefile $ helm install stable/mariadb --set master.persistence.storageClass="${STORAGE_CLASS}"
  • 41. Spinnaker + Helm ● Spinnaker의 Helm bake 기능을 활용과 연계 https://www.spinnaker.io/guides/user/kubernetes-v2/deploy-helm/
  • 42. Monocular + Helm ● Monocular와 Helm repository를 연계해 앱 마켓플레이스 활용 https://github.com/helm/monocular
  • 44. Chart의 설정 변경 #1 매개변수 사용 ● Chart source repository 문서의 설정 정보를 참고하여 설정 변경 $ helm install stable/mariadb --set image.tag=x.x.x https://github.com/helm/charts/tree/master/stable/mariadb
  • 45. Chart의 설정 변경 #2 파일 사용 ● yaml file 형태로 설정 변경도 가능. Chart의 values.yaml의 형식을 참고해서 작 성 $ cat values.yaml image: tag: x.x.x ... $ helm install stable/mariadb -f values.yaml
  • 47. Helm chart contribution ● 내가 만든 애플리케이션을 kubernetes helm repository에 배포하고 싶다면?
  • 48. Tips for contribution 1. Kubernetes helm code repository fork 2. 아래 가이드 참고하여 contributor 서명 후 commit a. https://github.com/helm/charts/blob/master/CONTRIBUTING.md 3. “helm create”로 만들어진 최신 버전 chart를 참고하여 내가 만든 chart 검토 4. Guidelines을 참고하여 내가 만든 chart 검토 a. https://github.com/helm/charts/blob/master/REVIEW_GUIDELINES.md 5. 내가 만든 chart를 incubator 디렉토리에 commit 6. Pull request!
  • 49. 참고자료 Helm 참고 자료 ● 블로그 : https://yunsangjun.github.io/blog/ Kubernetes 참고 자료 ● 블로그 : http://tech.cloudz-labs.io/
  • 50. Q & A