Kubernetes概念之deployment

一成天一成天的坐在辦公室，真的很~~~，懵圈中....，求解救。

本文經過《Kubernetes權威指南》的概念部分學習總結 

Deployment做用

Deployment與RC的做用實際上是同樣的，都是爲了管理Pod的副本數

 

Deployment的使用場景

1）建立一個Deployment對象來生成對應的Replica Set並完成Pod副本的建立過程。

2）檢查Deployment的狀態來看部署動做是否完成（Pod副本的數量是否達到了預期的值）

3）更新Deployment以建立新的Pod

4）若是當前Deployment不穩定，則回滾到一個早先的Deployment版本

5）掛起或者恢復一個Deployment

 

例子

建立一個deployment，管理一個運行tomcat的pod

 

一、建立deployment.yaml文件

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: frontend
spec:
  replicas: 1
  selector:
    matchLabels:
      tier: frontend
    matchExpressions:
      - {key: tier, operator: In, values: [frontend]}

  template:
    metadata:
      labels:
        app: app-demo
        tier: frontend
    spec:
      containers:
      - name: tomcat-demo
        image: tomcat
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 8080 

 

二、建立deployment

[root@master ~]# kubectl create -f tomcat-deployment.yaml 
deployment.extensions/frontend created

 

三、查看deployment信息

[root@master ~]# kubectl get deployment
NAME       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
frontend   1         1         1            1           23s

 

輸出結果的含義：

DESIRED：Pod副本數量的指望值，即deployment裏定義的Replica

CURRENT：當前Replica的值，這個值會不斷的增長，直到達到DESIRED爲止，代表整個部署過程完成

UP-TO-DATE：最新版本的Pod的副本數量，用於指示在滾動升級過程當中，有多少個Pod副本已經成功升級

AVAILABEL：當前集羣中可用的Pod副本數量，即集羣中當前存活的Pod數量

 

四、查看Pods信息

[root@master ~]# kubectl get pods
NAME                        READY     STATUS    RESTARTS   AGE
frontend-6cfdb4d686-j8jj7   1/1       Running   0          9m

 

五、查看deployment的詳細信息

[root@master ~]# kubectl describe deployment
Name:                   frontend
Namespace:              default
CreationTimestamp:      Fri, 20 Sep 2019 06:40:40 +0000
Labels:                 app=app-demo
                        tier=frontend
Annotations:            deployment.kubernetes.io/revision=1
Selector:               tier=frontend,tier in (frontend)
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  1 max unavailable, 1 max surge
Pod Template:
  Labels:  app=app-demo
           tier=frontend
  Containers:
   tomcat-demo:
    Image:        tomcat
    Port:         8080/TCP
    Host Port:    0/TCP
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   frontend-6cfdb4d686 (1/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  9m    deployment-controller  Scaled up replica set frontend-6cfdb4d686 to 1