20201229 kubernetes (五)

課堂資料

Helm

Helm 改入

之前方式部署應用基本過程，編寫yaml

deployment
service
ingress
pod
... ...

如果使用之前方式部署單一應用，少數服務的應用比較適合

如部署微服務，可能有幾十個服務，每個服務都有一個yaml，要維護大量yaml文件，版本管理特別不方便。

使用 Helm 可以解決那些問題 ?

使用 helm 可以把這些yaml做一個整體管理
實現yaml高效復用
使用 helm 應用及別的版本管理

Helm 是 Kubernetes 的包管理工具，如`yum / apt`，可以方便的將之前打包好的`yaml`文件部署到`k8s`上

Helm：命令行客戶端工具，用於k8s應用chart的創建、打包、發布、管理
Chart：應用描述，描述k8s資源相關文件的集合
Release：基於chart部署文件實體一個chart被helm執行後產生對應一個release

Helm 2019出 v3 版本

v3刪除了tiller
release可以在不同命名空間重用
將chart推送到docker倉庫中

v3 之前版本

v3 版本

課堂練習

安裝 DashBoard

gedit dashboard.yaml

dashboard.yaml

apiVersion: v1
kind: Namespace
metadata:
  name: kubernetes-dashboard

---

apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard

---

kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  type: NodePort
  ports:
    - port: 443
      targetPort: 8443
      nodePort: 30310
  selector:
    k8s-app: kubernetes-dashboard

---

apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-certs
  namespace: kubernetes-dashboard
type: Opaque

---

apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-csrf
  namespace: kubernetes-dashboard
type: Opaque
data:
  csrf: ""

---

apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-key-holder
  namespace: kubernetes-dashboard
type: Opaque

---

kind: ConfigMap
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-settings
  namespace: kubernetes-dashboard

---

kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
rules:
  # Allow Dashboard to get, update and delete Dashboard exclusive secrets.
  - apiGroups: [""]
    resources: ["secrets"]
    resourceNames: ["kubernetes-dashboard-key-holder", "kubernetes-dashboard-certs", "kubernetes-dashboard-csrf"]
    verbs: ["get", "update", "delete"]
    # Allow Dashboard to get and update 'kubernetes-dashboard-settings' config map.
  - apiGroups: [""]
    resources: ["configmaps"]
    resourceNames: ["kubernetes-dashboard-settings"]
    verbs: ["get", "update"]
    # Allow Dashboard to get metrics.
  - apiGroups: [""]
    resources: ["services"]
    resourceNames: ["heapster", "dashboard-metrics-scraper"]
    verbs: ["proxy"]
  - apiGroups: [""]
    resources: ["services/proxy"]
    resourceNames: ["heapster", "http:heapster:", "https:heapster:", "dashboard-metrics-scraper", "http:dashboard-metrics-scraper"]
    verbs: ["get"]

---

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
rules:
  # Allow Metrics Scraper to get metrics from the Metrics server
  - apiGroups: ["metrics.k8s.io"]
    resources: ["pods", "nodes"]
    verbs: ["get", "list", "watch"]

---

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: kubernetes-dashboard
subjects:
  - kind: ServiceAccount
    name: kubernetes-dashboard
    namespace: kubernetes-dashboard

---

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kubernetes-dashboard
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kubernetes-dashboard
subjects:
  - kind: ServiceAccount
    name: kubernetes-dashboard
    namespace: kubernetes-dashboard

---

kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: kubernetes-dashboard
  template:
    metadata:
      labels:
        k8s-app: kubernetes-dashboard
    spec:
      containers:
        - name: kubernetes-dashboard
          image: kubernetesui/dashboard:v2.0.0-beta7
          imagePullPolicy: Always
          ports:
            - containerPort: 8443
              protocol: TCP
          args:
            - --auto-generate-certificates
            - --namespace=kubernetes-dashboard
            # Uncomment the following line to manually specify Kubernetes API server Host
            # If not specified, Dashboard will attempt to auto discover the API server and connect
            # to it. Uncomment only if the default does not work.
            # - --apiserver-host=http://my-address:port
          volumeMounts:
            - name: kubernetes-dashboard-certs
              mountPath: /certs
              # Create on-disk volume to store exec logs
            - mountPath: /tmp
              name: tmp-volume
          livenessProbe:
            httpGet:
              scheme: HTTPS
              path: /
              port: 8443
            initialDelaySeconds: 30
            timeoutSeconds: 30
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            runAsUser: 1001
            runAsGroup: 2001
      volumes:
        - name: kubernetes-dashboard-certs
          secret:
            secretName: kubernetes-dashboard-certs
        - name: tmp-volume
          emptyDir: {}
      serviceAccountName: kubernetes-dashboard
      nodeSelector:
        "beta.kubernetes.io/os": linux
      # Comment the following tolerations if Dashboard must not be deployed on master
      tolerations:
        - key: node-role.kubernetes.io/master
          effect: NoSchedule

---

kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: dashboard-metrics-scraper
  name: dashboard-metrics-scraper
  namespace: kubernetes-dashboard
spec:
  ports:
    - port: 8000
      targetPort: 8000
  selector:
    k8s-app: dashboard-metrics-scraper

---

kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    k8s-app: dashboard-metrics-scraper
  name: dashboard-metrics-scraper
  namespace: kubernetes-dashboard
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: dashboard-metrics-scraper
  template:
    metadata:
      labels:
        k8s-app: dashboard-metrics-scraper
      annotations:
        seccomp.security.alpha.kubernetes.io/pod: 'runtime/default'
    spec:
      containers:
        - name: dashboard-metrics-scraper
          image: kubernetesui/metrics-scraper:v1.0.1
          ports:
            - containerPort: 8000
              protocol: TCP
          livenessProbe:
            httpGet:
              scheme: HTTP
              path: /
              port: 8000
            initialDelaySeconds: 30
            timeoutSeconds: 30
          volumeMounts:
          - mountPath: /tmp
            name: tmp-volume
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            runAsUser: 1001
            runAsGroup: 2001
      serviceAccountName: kubernetes-dashboard
      nodeSelector:
        "beta.kubernetes.io/os": linux
      # Comment the following tolerations if Dashboard must not be deployed on master
      tolerations:
        - key: node-role.kubernetes.io/master
          effect: NoSchedule
      volumes:
        - name: tmp-volume
          emptyDir: {}

kubectl apply -f dashboard.yaml

kubectl get deployment -n kubernetes-dashboard | grep dashboard

kubectl get all -n kubernetes-dashboard

gedit admin-role.yaml

admin-role.yaml

kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1                                                                           
metadata:
  name: admin
  annotations:
    rbac.authorization.kubernetes.io/autoupdate: "true"
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
  name: admin
  namespace: kube-system
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin
  namespace: kube-system
  labels:
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile

kubectl apply -f admin-role.yaml

取得帳戶 Token

kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep admin | awk '{print $1}') | grep token: | awk -F : '{print $2}' | xargs echo

Token

eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi10b2tlbi1tOGxwcCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJhZG1pbiIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6IjZiMmY5M2ZmLWE1MTYtNGI5Yi1iOTQyLTgyMTEwYWMxOTcwZCIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlLXN5c3RlbTphZG1pbiJ9.IcR8aIX5i8ZZXu2ps4_xAaf8zdCgSJg21ZwOi5v6c44DAl3VE3RcudD7RePtYUyLu4SdXdK1ewlcFY32nqlVJaUodXp2ULfRdqyks4HZD0nYV65eKM6poQI-in5SX53I8ygQjzlL3txBF8rMYCQNV_TCoFp48JILZRrUoeeW3pcSaZn-yLgDqHTd1N-MVHh-wlXU9U4kMen0DK_yOQ5nEsqwMVrei3ME8wo9gWcxYDZidR_Nc_pD421IK8AeHuNewuJMQSP7KC4bxXPDGMIcGfYh5arKnIXliDKEd5koMOjH-K8b4HinAecQR2Rp-vjsQb1k4UpJi1WYgwXu2BpbDw

vm1 瀏覽器輸入以下URL

https://192.168.8.129:30310/#!/login

取得的一串文字貼至 Web UI 的 Token 欄位進行登入

安裝 Helm ( v3 )

wget https://get.helm.sh/helm-v3.4.2-linux-amd64.tar.gz

tar xvfz helm-v3.4.2-linux-amd64.tar.gz

cd linux-amd64/

mv helm /usr/local/bin

helm version

初始化

helm repo add stable https://charts.helm.sh/stable

helm search repo stable

新增

helm repo add aliyun https://kubernetes.oss-cn-hangzhou.aliyuncs.com/charts

查看倉庫

helm repo ls

移除

helm repo remove [repoName]

安装Chart

helm repo update

helm install stable/mysql --generate-name

查詢資料庫

helm search repo mysql

helm ls

卸載一个版本

helm uninstall [helmName]

創建資料夾

cd

helm create abc

ls

cd abc

cd templates/

rm -rf *

gedit deployment.yaml service.yaml &

deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    app: web1
  name: web1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: web1
  strategy: {}
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: web1
    spec:
      containers:
      - image: httpd:2.4.46
        name: httpd
        resources: {}
status: {}

service.yaml

apiVersion: v1
kind: Service
metadata:
  creationTimestamp: null
  labels:
    app: web1
  name: web1
spec:
  ports:
  - port: 80
    protocol: TCP
    targetPort: 80
  selector:
    app: web1
  type: NodePort
status:
  loadBalancer: {}

ls

cd

ls

helm install abc --generate-name

helm ls

kubectl get deployment

kubectl get service

curl 192.168.8.129:[servicePorts]

Previous20201222 kubernetes (四)Next20210105 期末週

Last updated 4 years ago

課堂資料

Helm

Helm 改入

使用 Helm 可以解決那些問題 ?

Helm 是 Kubernetes 的包管理工具，如yum / apt，可以方便的將之前打包好的yaml文件部署到k8s上

Helm 2019出 v3 版本

v3 之前版本

v3 版本

課堂練習

安裝 DashBoard

dashboard.yaml

admin-role.yaml

安裝 Helm ( v3 )

初始化

新增

查看倉庫

移除

安装Chart

查詢資料庫

卸載一个版本

創建資料夾

deployment.yaml

service.yaml

課堂資料

Helm

Helm 改入

使用 Helm 可以解決那些問題 ?

Helm 是 Kubernetes 的包管理工具，如yum / apt，可以方便的將之前打包好的yaml文件部署到k8s上

Helm 2019出 v3 版本

v3 之前版本

v3 版本

課堂練習

安裝 DashBoard

dashboard.yaml

admin-role.yaml

安裝 Helm ( v3 )

初始化

新增

查看倉庫

移除

安装Chart

查詢資料庫

卸載一个版本

創建資料夾

deployment.yaml

service.yaml

Helm 是 Kubernetes 的包管理工具，如`yum / apt`，可以方便的將之前打包好的`yaml`文件部署到`k8s`上

Helm 是 Kubernetes 的包管理工具，如`yum / apt`，可以方便的將之前打包好的`yaml`文件部署到`k8s`上