天天看點
傳回

Kubernetes叢集中基于 CRD 實作分批釋出使用kubectl進行分批釋出釋出第二批

分批釋出是一種通用的釋出方式，但是在Kubernetes叢集中，要實作分批釋出，需要控制各種狀态，維護service流量，以及各種label配置，十分麻煩。阿裡雲容器服務提供一種基于 CRD 的分批釋出方式，大大友善釋出流程。

使用kubectl進行分批釋出

新叢集預設安裝了alicloud-application-controller，老叢集請先手動安裝，安裝方式，

kubectl create -f alicloud-application-controller.yml

 
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: alicloud-application-controller
  labels:
    owner: aliyun
    app: alicloud-application-controller
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      owner: aliyun
      app: alicloud-application-controller
  template:
    metadata:
      labels:
        owner: aliyun
        app: alicloud-application-controller
      annotations:
        scheduler.alpha.kubernetes.io/critical-pod: ''
    spec:
      tolerations:
      - effect: NoSchedule
        operator: Exists
        key: node-role.kubernetes.io/master
      - effect: NoSchedule
        operator: Exists
        key: node.cloudprovider.kubernetes.io/uninitialized
      containers:
        - name: alicloud-application-controller
          image: registry.cn-hangzhou.aliyuncs.com/acs/aliyun-app-lifecycle-manager:0.1-c8d5da8
          imagePullPolicy: IfNotPresent
      serviceAccount: admin

我們這裡以下面這個

StatefulSet

為例子示範分批釋出的流程，

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web
spec:
  selector:
    matchLabels:
      app: nginx # has to match .spec.template.metadata.labels
  serviceName: "nginx"
  replicas: 3 # by default is 1
  template:
    metadata:
      labels:
        app: nginx # has to match .spec.selector.matchLabels
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: nginx
        image: registry.cn-hangzhou.aliyuncs.com/xianlu/old-nginx
        ports:
        - containerPort: 80
          name: web

這是一個含有三個執行個體的nginx 執行個體，為了暴露此容器，我們使用Service來暴露，Service的Yaml如下

apiVersion: v1
kind: Service
metadata:
  name: nginx
  labels:
    app: nginx
spec:
  ports:
  - port: 80
    name: web
  selector:
    app: nginx
  type: LoadBalancer

這裡通過SLB 暴露nginx 服務。

為了保證使用者的Yaml安全性，分批釋出需要使用Secret來存儲最終的yaml，這裡需要将yaml執行一下base64操作，再存儲。

這個是

StatefulSet

的Secret Yaml

apiVersion: v1
kind: Secret
metadata:
  name: mysts
type: Opaque
data:
  yaml: YXBpVmVyc2lvbjogYXBwcy92MQpraW5kOiBTdGF0ZWZ1bFNldAptZXRhZGF0YToKICBuYW1lOiB3ZWIKc3BlYzoKICBzZWxlY3RvcjoKICAgIG1hdGNoTGFiZWxzOgogICAgICBhcHA6IG5naW54ICMgaGFzIHRvIG1hdGNoIC5zcGVjLnRlbXBsYXRlLm1ldGFkYXRhLmxhYmVscwogIHNlcnZpY2VOYW1lOiAibmdpbngiCiAgcmVwbGljYXM6IDMgIyBieSBkZWZhdWx0IGlzIDEKICB0ZW1wbGF0ZToKICAgIG1ldGFkYXRhOgogICAgICBsYWJlbHM6CiAgICAgICAgYXBwOiBuZ2lueCAjIGhhcyB0byBtYXRjaCAuc3BlYy5zZWxlY3Rvci5tYXRjaExhYmVscwogICAgc3BlYzoKICAgICAgdGVybWluYXRpb25HcmFjZVBlcmlvZFNlY29uZHM6IDEwCiAgICAgIGNvbnRhaW5lcnM6CiAgICAgIC0gbmFtZTogbmdpbngKICAgICAgICBpbWFnZTogcmVnaXN0cnkuY24taGFuZ3pob3UuYWxpeXVuY3MuY29tL3hpYW5sdS9vbGQtbmdpbngKICAgICAgICBwb3J0czoKICAgICAgICAtIGNvbnRhaW5lclBvcnQ6IDgwCiAgICAgICAgICBuYW1lOiB3ZWI=

下面的為Service的Secret Yaml

apiVersion: v1
kind: Secret
metadata:
  name: mysvc
type: Opaque
data:
  yaml: YXBpVmVyc2lvbjogdjEKa2luZDogU2VydmljZQptZXRhZGF0YToKICBuYW1lOiBuZ2lueAogIGxhYmVsczoKICAgIGFwcDogbmdpbngKc3BlYzoKICBwb3J0czoKICAtIHBvcnQ6IDgwCiAgICBuYW1lOiB3ZWIKICBzZWxlY3RvcjoKICAgIGFwcDogbmdpbngKICB0eXBlOiBMb2FkQmFsYW5jZXI=

分别将上面的兩個Secret 建立出來，kubectl create -f xxxxx

​

Kubernetes叢集中基于 CRD 實作分批釋出使用kubectl進行分批釋出釋出第二批

可以看到兩個Secret都已經建立完畢，下面就可以來建立分批釋出的 CRD。分批釋出的 CRD 格式如下，

apiVersion: alicloud.com/v1beta1
kind: BatchRelease
metadata:
  name: example-batch-release
  annotations:
    aliyun.batchnum: "2"
spec:
  statefulSetSecretName: mysts
  serviceSecretName: mysvc

�

aliyun.batchnum

: 代表分幾批釋出，目前預設是2批

statefulSetSecretName

: 表示存儲StatefulSet的Secret 名稱

serviceSecretName

: 表示存儲Service的Secret 名稱

使用

kubectl create -f xxx

建立此CRD分批釋出

Kubernetes叢集中基于 CRD 實作分批釋出使用kubectl進行分批釋出釋出第二批

可以看到，描述資源都已經建立出來了。

[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get sts
NAME      DESIRED   CURRENT   AGE
web       3         3         6m
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get pods -o=wide
NAME      READY     STATUS    RESTARTS   AGE       IP             NODE
web-0     1/1       Running   0          7m        172.16.2.2     cn-hangzhou.i-bp199b7a244chaux4ozh
web-1     1/1       Running   0          6m        172.16.2.131   cn-hangzhou.i-bp199b7a244chaux4ozi
web-2     1/1       Running   0          6m        172.16.1.136   cn-hangzhou.i-bp199b7a244chaux4ozg
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get svc
NAME         TYPE           CLUSTER-IP      EXTERNAL-IP      PORT(S)        AGE
kubernetes   ClusterIP      172.19.0.1      <none>           443/TCP        4h
nginx        LoadBalancer   172.19.12.163   120.55.148.238   80:32065/TCP   7m
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# curl 120.55.148.238
old

可以看到，nginx 的StatefulSet和對應的Service 都已經建立出來，并且curl 是可以直接通路。

下面我們開始分批釋出一個新版本的StatefulSet，這裡我們新的StatefulSet Yaml 模闆如下

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web
spec:
  selector:
    matchLabels:
      app: nginx # has to match .spec.template.metadata.labels
  serviceName: "nginx"
  replicas: 3 # by default is 1
  template:
    metadata:
      labels:
        app: nginx # has to match .spec.selector.matchLabels
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: nginx
        image: registry.cn-hangzhou.aliyuncs.com/xianlu/new-nginx
        ports:
        - containerPort: 80
          name: web

可以看到，新老StatefulSet的差別在于，更換了新版本的鏡像。

同樣，我們需要建立一個Secret 來存儲這個新的StatefulSet

apiVersion: v1
kind: Secret
metadata:
  name: my-new-sts
type: Opaque
data:
  yaml: YXBpVmVyc2lvbjogYXBwcy92MQpraW5kOiBTdGF0ZWZ1bFNldAptZXRhZGF0YToKICBuYW1lOiB3ZWIKc3BlYzoKICBzZWxlY3RvcjoKICAgIG1hdGNoTGFiZWxzOgogICAgICBhcHA6IG5naW54ICMgaGFzIHRvIG1hdGNoIC5zcGVjLnRlbXBsYXRlLm1ldGFkYXRhLmxhYmVscwogIHNlcnZpY2VOYW1lOiAibmdpbngiCiAgcmVwbGljYXM6IDMgIyBieSBkZWZhdWx0IGlzIDEKICB0ZW1wbGF0ZToKICAgIG1ldGFkYXRhOgogICAgICBsYWJlbHM6CiAgICAgICAgYXBwOiBuZ2lueCAjIGhhcyB0byBtYXRjaCAuc3BlYy5zZWxlY3Rvci5tYXRjaExhYmVscwogICAgc3BlYzoKICAgICAgdGVybWluYXRpb25HcmFjZVBlcmlvZFNlY29uZHM6IDEwCiAgICAgIGNvbnRhaW5lcnM6CiAgICAgIC0gbmFtZTogbmdpbngKICAgICAgICBpbWFnZTogcmVnaXN0cnkuY24taGFuZ3pob3UuYWxpeXVuY3MuY29tL3hpYW5sdS9uZXctbmdpbngKICAgICAgICBwb3J0czoKICAgICAgICAtIGNvbnRhaW5lclBvcnQ6IDgwCiAgICAgICAgICBuYW1lOiB3ZWI=

然後我們更新剛才建立的 CRD，将statefulSetSecretName改成新的StatefulSet名稱。

修改後的CRD Yaml 如下:

[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get BatchRelease example-batch-release -o=yaml
apiVersion: alicloud.com/v1beta1
kind: BatchRelease
metadata:
  annotations:
    aliyun.batchnum: "2"
  clusterName: ""
  creationTimestamp: 2018-07-31T08:17:17Z
  generation: 1
  name: example-batch-release
  namespace: default
  resourceVersion: "43484"
  selfLink: /apis/alicloud.com/v1beta1/namespaces/default/batchreleases/example-batch-release
  uid: 2386ddfd-949a-11e8-a3c2-00163e086528
spec:
  serviceSecretName: mysvc
  statefulSetSecretName: my-new-sts
           
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl describe BatchRelease example-batch-release
Name:         example-batch-release
Namespace:    default
Labels:       <none>
Annotations:  aliyun.batchnum=2
API Version:  alicloud.com/v1beta1
Kind:         BatchRelease
Metadata:
  Cluster Name:
  Creation Timestamp:  2018-07-31T08:17:17Z
  Generation:          1
  Resource Version:    43484
  Self Link:           /apis/alicloud.com/v1beta1/namespaces/default/batchreleases/example-batch-release
  UID:                 2386ddfd-949a-11e8-a3c2-00163e086528
Spec:
  Service Secret Name:       mysvc
  Stateful Set Secret Name:  my-new-sts
Status:
  Control:
  Release:
    Batch _ Order:  1
    Progress:       finished
    Status:         WaitingForConfirm
  Resources:
    Service:
      Name:       nginx
      Namespace:  default
      Status:     Updating
    Stateful Set:
      Name:       web
      Namespace:  default
      Status:     Updating
Events:
  Type    Reason             Age   From               Message
  ----    ------             ----  ----               -------
  Normal  CreateSubResource  2m    aliyun-controller  Create StatefulSet resource sucessfully
  Normal  CreateSubResource  2m    aliyun-controller  Create service resource sucessfully
  Normal  Synced             2m    aliyun-controller  Batch CRD synced successfully
  Normal  UpdateResource     1m    aliyun-controller  Begin to update StatefulSet web with partition 2
  Normal  UpdateResource     1m    aliyun-controller  Waiting StatefulSet default:web ready, readyReplicas 2 replicas 3 times 1
  Normal  UpdateResource     1m    aliyun-controller  Waiting StatefulSet default:web ready, readyReplicas 2 replicas 3 times 2
  Normal  UpdateResource     1m    aliyun-controller  Begin to update service with new selector map[app:nginx aliyun.version:2]
  Normal  UpdateResource     1m    aliyun-controller  Update StatefulSet and Service sucessfully, waiting confirm
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get pods -o=wide
NAME      READY     STATUS    RESTARTS   AGE       IP             NODE
web-0     1/1       Running   0          2m        172.16.2.132   cn-hangzhou.i-bp199b7a244chaux4ozi
web-1     1/1       Running   0          2m        172.16.2.3     cn-hangzhou.i-bp199b7a244chaux4ozh
web-2     1/1       Running   0          1m        172.16.1.138   cn-hangzhou.i-bp199b7a244chaux4ozg
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get svc
NAME         TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)        AGE
kubernetes   ClusterIP      172.19.0.1     <none>           443/TCP        5h
nginx        LoadBalancer   172.19.2.184   101.37.107.187   80:32173/TCP   2m
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# curl 101.37.107.187
new
[root@iZbp11x2k7by5gfy6pkrl1Z ~]#

我們可以通過event 看到 CRD 的所有事件。同時可以看到，nginx的3個pod，已經有一個 pod發生了改變，變成了最新鏡像，同時 curl對應的service，會發現流量已經指向了新的pod。這樣使用者就可以快速試錯了。

下面我們來示範如何快速復原，如果流量打到新的 pod後發現有問題，需要復原，那麼我們需要編輯CRD,

Kubernetes叢集中基于 CRD 實作分批釋出使用kubectl進行分批釋出釋出第二批

将Status 的action 置為rollback 就可以快速復原。

[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl edit BatchRelease example-batch-release
batchrelease.alicloud.com "example-batch-release" edited
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get pods -o=wide
NAME      READY     STATUS    RESTARTS   AGE       IP             NODE
web-0     1/1       Running   0          7m        172.16.2.132   cn-hangzhou.i-bp199b7a244chaux4ozi
web-1     1/1       Running   0          7m        172.16.2.3     cn-hangzhou.i-bp199b7a244chaux4ozh
web-2     1/1       Running   0          3s        172.16.1.139   cn-hangzhou.i-bp199b7a244chaux4ozg
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get svc
NAME         TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)        AGE
kubernetes   ClusterIP      172.19.0.1     <none>           443/TCP        5h
nginx        LoadBalancer   172.19.2.184   101.37.107.187   80:32173/TCP   7m
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# curl 101.37.107.187
old

可以看到原來web-2所在的pod已經被復原到了老鏡像，現在curl service 也都是老的服務了。

釋出第二批

Kubernetes叢集中基于 CRD 實作分批釋出使用kubectl進行分批釋出釋出第二批

釋出第二批需要在action 置為continue 就可以

[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get pods -o=wide
NAME      READY     STATUS    RESTARTS   AGE       IP             NODE
web-0     1/1       Running   0          3s        172.16.2.138   cn-hangzhou.i-bp199b7a244chaux4ozi
web-1     1/1       Running   0          13s       172.16.2.12    cn-hangzhou.i-bp199b7a244chaux4ozh
web-2     1/1       Running   0          2m        172.16.1.153   cn-hangzhou.i-bp199b7a244chaux4ozg
[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get BatchRelease example-batch-release -o=yaml
apiVersion: alicloud.com/v1beta1
kind: BatchRelease
metadata:
  annotations:
    aliyun.batchnum: "2"
  clusterName: ""
  creationTimestamp: 2018-07-31T09:44:58Z
  generation: 1
  name: example-batch-release
  namespace: default
  resourceVersion: "58066"
  selfLink: /apis/alicloud.com/v1beta1/namespaces/default/batchreleases/example-batch-release
  uid: 6321dcaf-94a6-11e8-a3c2-00163e086528
spec:
  serviceSecretName: mysvc
  statefulSetSecretName: my-new-sts
status:
  control: {}
  release:
    batch_order: "2"
    progress: finished
    status: WaitingForConfirm
  resources:
    Service:
      name: nginx
      namespace: default
      status: Updating
    StatefulSet:
      name: web
      namespace: default
      status: Updating

可以看到StatefulSet的三個 pod都被更新了。

這個時候就可以确認釋出了

Kubernetes叢集中基于 CRD 實作分批釋出使用kubectl進行分批釋出釋出第二批

置為confirm 就确定了這次釋出。

[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get BatchRelease example-batch-release -o=yaml
apiVersion: alicloud.com/v1beta1
kind: BatchRelease
metadata:
  annotations:
    aliyun.batchnum: "2"
  clusterName: ""
  creationTimestamp: 2018-07-31T09:44:58Z
  generation: 1
  name: example-batch-release
  namespace: default
  resourceVersion: "58542"
  selfLink: /apis/alicloud.com/v1beta1/namespaces/default/batchreleases/example-batch-release
  uid: 6321dcaf-94a6-11e8-a3c2-00163e086528
spec:
  serviceSecretName: mysvc
  statefulSetSecretName: my-new-sts
status:
  control: {}
  release:
    progress: finished
    status: Success
  resources:
    Service:
      name: nginx
      namespace: default
      status: Success
    StatefulSet:
      name: web
      namespace: default
      status: Success


[root@iZbp11x2k7by5gfy6pkrl1Z ~]# kubectl get secret -l owner=aliyun -n=kube-system
NAME                       TYPE      DATA      AGE
example-batch-release.v1   Opaque    4         18m
example-batch-release.v2   Opaque    4         56s

可以看到，所有的确認版本曆史都會被記錄到secret裡面，友善到時候跨版本復原。

應用服務中間件 nginx 容器 kubernetes 網絡協定 perl 存儲 Python api Kubernetes叢集監控 kubernetes叢集建立 kubernetes叢集排程 Kubernetes叢集叢集 搭建Kubernetes叢集
上一篇: 快成物流完成億元級Pre-A輪融資，為公路貨運作業提供一體化的智慧物流解決方案
下一篇: 11連勝！絕藝橫掃中美日韓對手，稱霸圍棋AI世界大戰

繼續閱讀