2. 程式人生 > >k8s基本概念-如何使用Deployments

k8s基本概念-如何使用Deployments

阿新 • • 發佈：2018-01-19
available time env source sources blob set nav sting

k8s基本概念-如何使用Deployments

2018/1/5

Deployments 使用示例

  • 創建一個 app
  • 查看 app 狀態
  • 更新 app
  • 回滾 app
  • 擴縮容 app
  • 刪除 app
創建一個 app

  • 通過 yaml 配置文件來定義 Deployment

    • 關於 apiVersion 的寫法，請參考：
    • https://github.com/kubernetes/kubernetes/blob/630dbedef9de9ef678f16132796b103b8a03fcda/pkg/api/testing/defaulting_test.go
    • 關於 metadata 中的 name
    • 定義來 deployment 的名稱
    • 同一個 namespace 下名稱不能重復
    • 關於 metadata 中的 labels
    • k/v 鍵值對
    • key 的命名規則
      • 必須
      • 包含一個可選的 prefix 和 name 並小於 64 字符
      • name 以字母和數字 [a-z0-9A-Z] 開頭和結尾，中間可以是 dashes (-)，underscores (_)，dots (.)，字母和數字
      • prefix 是可選的，類似這樣："kubernetes.io/" 暫不討論
    • Value 的命名規則
      • 可以為空，或小於 64 字符
      • 以字母和數字 [a-z0-9A-Z] 開頭和結尾，中間可以是 dashes (-)，underscores (_)，dots (.)，字母和數字
    • 關於 metadata 中的 namespace
    • 默認使用 default 
      [root@tvm-00 ~]# cat ~/k8s_install/test/whoami/app.yaml
apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
name: test-deployment-app-whoami
labels:
app: whoami
spec:
replicas: 3
selector:
matchLabels:
app: whoami
template:
metadata:
labels:
app: whoami
spec:
containers:
- name: whoami
  image: opera443399/whoami:0.9
  ports:
    - containerPort: 80
  • 運行 app 
    ### 註意：使用 --record 可以記錄指令的 history 便於後續 rolling update 選擇
[root@tvm-00 ~]# kubectl apply -f ~/k8s_install/test/whoami/app.yaml --record
deployment "test-deployment-app-whoami" created
查看 app 狀態
  • 查看信息 
    [root@tvm-00 ~]# kubectl get deployments
NAME                         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
test-deployment-app-whoami   3         3         3            3           5m
[root@tvm-00 ~]# kubectl get rs
NAME                                    DESIRED   CURRENT   READY     AGE
test-deployment-app-whoami-6cf9cd6bf4   3         3         3         5m
[root@tvm-00 ~]# kubectl get pods
NAME                                          READY     STATUS    RESTARTS   AGE
test-deployment-app-whoami-6cf9cd6bf4-59h9x   1/1       Running   0          5m
test-deployment-app-whoami-6cf9cd6bf4-978ht   1/1       Running   0          5m
test-deployment-app-whoami-6cf9cd6bf4-w5dhk   1/1       Running   0          5m
[root@tvm-00 ~]# kubectl get pods --show-labels
NAME                                          READY     STATUS    RESTARTS   AGE       LABELS
test-deployment-app-whoami-6cf9cd6bf4-59h9x   1/1       Running   0          7m        app=whoami,pod-template-hash=2795782690
test-deployment-app-whoami-6cf9cd6bf4-978ht   1/1       Running   0          7m        app=whoami,pod-template-hash=2795782690
test-deployment-app-whoami-6cf9cd6bf4-w5dhk   1/1       Running   0          7m        app=whoami,pod-template-hash=2795782690
更新 app
  • 試著更新 1 次鏡像後，查看信息，重點留意版本歷史 
    
### 更新 image 為其他版本：
[root@tvm-00 ~]# kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.7
deployment "test-deployment-app-whoami" image updated

查看信息

[root@tvm-00 ~]# kubectl rollout status deployments/test-deployment-app-whoami
deployment "test-deployment-app-whoami" successfully rolled out
[root@tvm-00 ~]# kubectl get deployments
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
test-deployment-app-whoami 3 3 3 3 11m
[root@tvm-00 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
test-deployment-app-whoami-68c6cd964 3 3 3 42s
test-deployment-app-whoami-6cf9cd6bf4 0 0 0 11m
[root@tvm-00 ~]# kubectl get pods
NAME READY STATUS RESTARTS AGE
test-deployment-app-whoami-68c6cd964-bfznh 1/1 Running 0 54s
test-deployment-app-whoami-68c6cd964-r7vp5 1/1 Running 0 56s
test-deployment-app-whoami-68c6cd964-vssrj 1/1 Running 0 53s

[root@tvm-00 ~]# kubectl describe deployments/test-deployment-app-whoami
Name: test-deployment-app-whoami
Namespace: default
CreationTimestamp: Wed, 27 Dec 2017 17:44:30 +0800
Labels: app=whoami
Annotations: deployment.kubernetes.io/revision=2
kubectl.kubernetes.io/last-applied-configuration=（略）
kubernetes.io/change-cause=kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.7
Selector: app=whoami
Replicas: 3 desired		 3 updated 3 total 3 available 0 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 25% max unavailable, 25% max surge
Pod Template:
Labels: app=whoami
Containers:
whoami:
Image: opera443399/whoami:0.7
Port: 80/TCP
Environment: <none>
Mounts: <none>
Volumes: <none>
Conditions:
Type Status Reason

Available True MinimumReplicasAvailable
Progressing True NewReplicaSetAvailable
OldReplicaSets: <none>
NewReplicaSet: test-deployment-app-whoami-68c6cd964 (3/3 replicas created)
Events:
Type Reason Age From Message

Normal ScalingReplicaSet 12m deployment-controller Scaled up replica set test-deployment-app-whoami-6cf9cd6bf4 to 3
Normal ScalingReplicaSet 1m deployment-controller Scaled up replica set test-deployment-app-whoami-68c6cd964 to 1
Normal ScalingReplicaSet 1m deployment-controller Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 2
Normal ScalingReplicaSet 1m deployment-controller Scaled up replica set test-deployment-app-whoami-68c6cd964 to 2
Normal ScalingReplicaSet 1m deployment-controller Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 1
Normal ScalingReplicaSet 1m deployment-controller Scaled up replica set test-deployment-app-whoami-68c6cd964 to 3
Normal ScalingReplicaSet 1m deployment-controller Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 0

[root@tvm-00 ~]# kubectl rollout history deployments/test-deployment-app-whoami
deployments "test-deployment-app-whoami"
REVISION CHANGE-CAUSE
1 kubectl apply --filename=/root/k8s_install/test/whoami/app.yaml --record=true
2 kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.7


- 再更新 1 次鏡像後，再次查看信息
```bash
[root@tvm-00 ~]# kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.8
deployment "test-deployment-app-whoami" image updated
[root@tvm-00 ~]# kubectl rollout status deployments/test-deployment-app-whoami
deployment "test-deployment-app-whoami" successfully rolled out
[root@tvm-00 ~]# kubectl get deployments
NAME                         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
test-deployment-app-whoami   3         3         3            3           17m
[root@tvm-00 ~]# kubectl get rs
NAME                                    DESIRED   CURRENT   READY     AGE
test-deployment-app-whoami-68b94dd7bf   3         3         3         46s
test-deployment-app-whoami-68c6cd964    0         0         0         6m
test-deployment-app-whoami-6cf9cd6bf4   0         0         0         17m
[root@tvm-00 ~]# kubectl get pods
NAME                                          READY     STATUS    RESTARTS   AGE
test-deployment-app-whoami-68b94dd7bf-5g89x   1/1       Running   0          45s
test-deployment-app-whoami-68b94dd7bf-75xjd   1/1       Running   0          52s
test-deployment-app-whoami-68b94dd7bf-pchpw   1/1       Running   0          49s
[root@tvm-00 ~]# kubectl describe deployments/test-deployment-app-whoami
Name:                   test-deployment-app-whoami
Namespace:              default
CreationTimestamp:      Wed, 27 Dec 2017 17:44:30 +0800
Labels:                 app=whoami
Annotations:            deployment.kubernetes.io/revision=3
                        kubectl.kubernetes.io/last-applied-configuration=（略）
                        kubernetes.io/change-cause=kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.8
Selector:               app=whoami
Replicas:               3 desired | 3 updated | 3 total | 3 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:  app=whoami
  Containers:
   whoami:
    Image:        opera443399/whoami:0.8
    Port:         80/TCP
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   test-deployment-app-whoami-68b94dd7bf (3/3 replicas created)
Events:
  Type    Reason             Age              From                   Message
  ----    ------             ----             ----                   -------
  Normal  ScalingReplicaSet  18m              deployment-controller  Scaled up replica set test-deployment-app-whoami-6cf9cd6bf4 to 3
  Normal  ScalingReplicaSet  7m               deployment-controller  Scaled up replica set test-deployment-app-whoami-68c6cd964 to 1
  Normal  ScalingReplicaSet  7m               deployment-controller  Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 2
  Normal  ScalingReplicaSet  7m               deployment-controller  Scaled up replica set test-deployment-app-whoami-68c6cd964 to 2
  Normal  ScalingReplicaSet  7m               deployment-controller  Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 1
  Normal  ScalingReplicaSet  7m               deployment-controller  Scaled up replica set test-deployment-app-whoami-68c6cd964 to 3
  Normal  ScalingReplicaSet  7m               deployment-controller  Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 0
  Normal  ScalingReplicaSet  2m               deployment-controller  Scaled up replica set test-deployment-app-whoami-68b94dd7bf to 1
  Normal  ScalingReplicaSet  2m               deployment-controller  Scaled down replica set test-deployment-app-whoami-68c6cd964 to 2
  Normal  ScalingReplicaSet  2m               deployment-controller  Scaled up replica set test-deployment-app-whoami-68b94dd7bf to 2
  Normal  ScalingReplicaSet  2m (x3 over 2m)  deployment-controller  (combined from similar events): Scaled down replica set test-deployment-app-whoami-68c6cd964 to 0
[root@tvm-00 ~]# kubectl rollout history deployments/test-deployment-app-whoami
deployments "test-deployment-app-whoami"
REVISION  CHANGE-CAUSE
1         kubectl apply --filename=/root/k8s_install/test/whoami/app.yaml --record=true
2         kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.7
3         kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.8

### 符合預期，我們現在有了 3 個版本
回滾 app
  • 回滾到上一個版本 
    
[root@tvm-00 ~]# kubectl rollout undo deployments/test-deployment-app-whoami
deployment "test-deployment-app-whoami"
[root@tvm-00 ~]# kubectl rollout history deployments/test-deployment-app-whoami
deployments "test-deployment-app-whoami"
REVISION  CHANGE-CAUSE
1         kubectl apply --filename=/root/k8s_install/test/whoami/app.yaml --record=true
3         kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.8
4         kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.7

[root@tvm-00 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
test-deployment-app-whoami-68b94dd7bf 0 0 0 16m
test-deployment-app-whoami-68c6cd964 3 3 3 22m
test-deployment-app-whoami-6cf9cd6bf4 0 0 0 33m

[root@tvm-00 ~]# kubectl describe deployments/test-deployment-app-whoami
Name: test-deployment-app-whoami
Namespace: default
CreationTimestamp: Wed, 27 Dec 2017 17:44:30 +0800
Labels: app=whoami
Annotations: deployment.kubernetes.io/revision=4
kubectl.kubernetes.io/last-applied-configuration=（略）
kubernetes.io/change-cause=kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.7
Selector: app=whoami
Replicas: 3 desired		 3 updated 3 total 3 available 0 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 25% max unavailable, 25% max surge
Pod Template:
Labels: app=whoami
Containers:
whoami:
Image: opera443399/whoami:0.7
Port: 80/TCP
Environment: <none>
Mounts: <none>
Volumes: <none>
Conditions:
Type Status Reason

Available True MinimumReplicasAvailable
Progressing True NewReplicaSetAvailable
OldReplicaSets: <none>
NewReplicaSet: test-deployment-app-whoami-68c6cd964 (3/3 replicas created)
Events:
Type Reason Age From Message

Normal ScalingReplicaSet 27m deployment-controller Scaled up replica set test-deployment-app-whoami-6cf9cd6bf4 to 3
Normal ScalingReplicaSet 17m deployment-controller Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 2
Normal ScalingReplicaSet 17m deployment-controller Scaled up replica set test-deployment-app-whoami-68c6cd964 to 2
Normal ScalingReplicaSet 17m deployment-controller Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 1
Normal ScalingReplicaSet 17m deployment-controller Scaled up replica set test-deployment-app-whoami-68c6cd964 to 3
Normal ScalingReplicaSet 16m deployment-controller Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 0
Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set test-deployment-app-whoami-68b94dd7bf to 1
Normal ScalingReplicaSet 11m deployment-controller Scaled down replica set test-deployment-app-whoami-68c6cd964 to 2
Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set test-deployment-app-whoami-68b94dd7bf to 2
Normal ScalingReplicaSet 1m (x2 over 17m) deployment-controller Scaled up replica set test-deployment-app-whoami-68c6cd964 to 1
Normal DeploymentRollback 1m deployment-controller Rolled back deployment "test-deployment-app-whoami" to revision 2
Normal ScalingReplicaSet 1m (x8 over 11m) deployment-controller (combined from similar events): Scaled down replica set test-deployment-app-whoami-68b94dd7bf to 0


- 回滾到指定的版本
```bash
[root@tvm-00 ~]# kubectl rollout undo deployments/test-deployment-app-whoami --to-revision=1
deployment "test-deployment-app-whoami"
[root@tvm-00 ~]# kubectl rollout history deployments/test-deployment-app-whoami
deployments "test-deployment-app-whoami"
REVISION  CHANGE-CAUSE
3         kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.8
4         kubectl set image deployments/test-deployment-app-whoami whoami=opera443399/whoami:0.7
5         kubectl apply --filename=/root/k8s_install/test/whoami/app.yaml --record=true

[root@tvm-00 ~]# kubectl get rs
NAME                                    DESIRED   CURRENT   READY     AGE
test-deployment-app-whoami-68b94dd7bf   0         0         0         16m
test-deployment-app-whoami-68c6cd964    0         0         0         22m
test-deployment-app-whoami-6cf9cd6bf4   3         3         3         33m

[root@tvm-00 ~]# kubectl describe deployments/test-deployment-app-whoami
Name:                   test-deployment-app-whoami
Namespace:              default
CreationTimestamp:      Wed, 27 Dec 2017 17:44:30 +0800
Labels:                 app=whoami
Annotations:            deployment.kubernetes.io/revision=5
                        kubectl.kubernetes.io/last-applied-configuration=（略）
                        kubernetes.io/change-cause=kubectl apply --filename=/root/k8s_install/test/whoami/app.yaml --record=true
Selector:               app=whoami
Replicas:               3 desired | 3 updated | 3 total | 3 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:  app=whoami
  Containers:
   whoami:
    Image:        opera443399/whoami:0.9
    Port:         80/TCP
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   test-deployment-app-whoami-6cf9cd6bf4 (3/3 replicas created)
Events:
  Type    Reason              Age                 From                   Message
  ----    ------              ----                ----                   -------
  Normal  ScalingReplicaSet   29m                 deployment-controller  Scaled up replica set test-deployment-app-whoami-6cf9cd6bf4 to 3
  Normal  ScalingReplicaSet   19m                 deployment-controller  Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 2
  Normal  ScalingReplicaSet   19m                 deployment-controller  Scaled up replica set test-deployment-app-whoami-68c6cd964 to 2
  Normal  ScalingReplicaSet   19m                 deployment-controller  Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 1
  Normal  ScalingReplicaSet   19m                 deployment-controller  Scaled up replica set test-deployment-app-whoami-68c6cd964 to 3
  Normal  ScalingReplicaSet   19m                 deployment-controller  Scaled down replica set test-deployment-app-whoami-6cf9cd6bf4 to 0
  Normal  ScalingReplicaSet   13m                 deployment-controller  Scaled up replica set test-deployment-app-whoami-68b94dd7bf to 1
  Normal  ScalingReplicaSet   13m                 deployment-controller  Scaled down replica set test-deployment-app-whoami-68c6cd964 to 2
  Normal  ScalingReplicaSet   13m                 deployment-controller  Scaled up replica set test-deployment-app-whoami-68b94dd7bf to 2
  Normal  ScalingReplicaSet   3m (x2 over 19m)    deployment-controller  Scaled up replica set test-deployment-app-whoami-68c6cd964 to 1
  Normal  DeploymentRollback  3m                  deployment-controller  Rolled back deployment "test-deployment-app-whoami" to revision 2
  Normal  DeploymentRollback  29s                 deployment-controller  Rolled back deployment "test-deployment-app-whoami" to revision 1
  Normal  ScalingReplicaSet   27s (x12 over 13m)  deployment-controller  (combined from similar events): Scaled up replica set test-deployment-app-whoami-6cf9cd6bf4 to 3
  Normal  ScalingReplicaSet   27s                 deployment-controller  Scaled down replica set test-deployment-app-whoami-68c6cd964 to 1
  Normal  ScalingReplicaSet   26s                 deployment-controller  Scaled down replica set test-deployment-app-whoami-68c6cd964 to 0
擴縮容 app
  • 擴容 
    
### 調整副本數量到 10 個
[root@tvm-00 ~]# kubectl scale deployments/test-deployment-app-whoami --replicas=10
deployment "test-deployment-app-whoami" scaled

查看信息

[root@tvm-00 ~]# kubectl get deployments
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
test-deployment-app-whoami 10 10 10 10 39m
[root@tvm-00 ~]# kubectl get rs
NAME DESIRED CURRENT READY AGE
test-deployment-app-whoami-68b94dd7bf 0 0 0 23m
test-deployment-app-whoami-68c6cd964 0 0 0 29m
test-deployment-app-whoami-6cf9cd6bf4 10 10 10 39m
[root@tvm-00 ~]# kubectl get pods
NAME READY STATUS RESTARTS AGE
test-deployment-app-whoami-6cf9cd6bf4-2dd5m 1/1 Running 0 36s
test-deployment-app-whoami-6cf9cd6bf4-4nx7x 1/1 Running 0 36s
test-deployment-app-whoami-6cf9cd6bf4-bb7v7 1/1 Running 0 10m
test-deployment-app-whoami-6cf9cd6bf4-c7cht 1/1 Running 0 36s
test-deployment-app-whoami-6cf9cd6bf4-dph22 1/1 Running 0 36s
test-deployment-app-whoami-6cf9cd6bf4-jhtqz 1/1 Running 0 10m
test-deployment-app-whoami-6cf9cd6bf4-jjfp5 1/1 Running 0 36s
test-deployment-app-whoami-6cf9cd6bf4-nlqq5 1/1 Running 0 36s
test-deployment-app-whoami-6cf9cd6bf4-px24h 1/1 Running 0 10m
test-deployment-app-whoami-6cf9cd6bf4-rldhd 1/1 Running 0 36s


- 縮容
```bash
### 調整副本數量到 5 個
[root@tvm-00 ~]# kubectl scale deployments/test-deployment-app-whoami --replicas=5
deployment "test-deployment-app-whoami" scaled

### 查看信息
[root@tvm-00 ~]# kubectl get deployments
NAME                         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
test-deployment-app-whoami   5         5         5            5           41m
[root@tvm-00 ~]# kubectl get rs
NAME                                    DESIRED   CURRENT   READY     AGE
test-deployment-app-whoami-68b94dd7bf   0         0         0         25m
test-deployment-app-whoami-68c6cd964    0         0         0         30m
test-deployment-app-whoami-6cf9cd6bf4   5         5         5         41m
[root@tvm-00 ~]# kubectl get pods
NAME                                          READY     STATUS    RESTARTS   AGE
test-deployment-app-whoami-6cf9cd6bf4-2dd5m   1/1       Running   0          2m
test-deployment-app-whoami-6cf9cd6bf4-bb7v7   1/1       Running   0          12m
test-deployment-app-whoami-6cf9cd6bf4-c7cht   1/1       Running   0          2m
test-deployment-app-whoami-6cf9cd6bf4-jhtqz   1/1       Running   0          12m
test-deployment-app-whoami-6cf9cd6bf4-px24h   1/1       Running   0          12m
刪除
[root@tvm-00 test]# kubectl delete deployments/test-deployment-app-whoami
deployment "test-deployment-app-whoami" deleted
[root@tvm-00 test]# kubectl get deployments
No resources found.

k8s基本概念-如何使用Deployments

相關推薦

k8s基本概念-如何使用Deployments

available time env source sources blob set nav sting k8s基本概念-如何使用Deployments 2018/1/5 Deployments 使用示例 創建一個 app 查看 app 狀態 更新 app 回滾 app

k8s基本概念-如何使用Services

-i -a beta image 所有 隨機 created prot 測試 k8s基本概念-如何使用Services 2018/1/5 Services 使用示例 Virtual IPs and service proxies Publishing services -

k8s基本概念-如何使用私有regsitry

10.10 基本概念 mage exe tps 如何 dep current accounts k8s基本概念-如何使用私有regsitry 2018/1/9 私有 regsitry 使用示例 準備資源 通過 secret 來使用 關聯到 serviceAccounts

k8s基本概念-配置調度策略之(Taints-and-Tolerations)

k8s taint toleration k8s基本概念-配置調度策略之(Taints-and-Tolerations) 2018/4/12 通過定義 Taints and Tolerations 來達到 node 排斥 pod 的目的 通過一個典型實例來描述 taint 和 toleratio

K8S 基本概念

manage sched etcd man docke 介紹 proxy pro 組件 一. 組件介紹 1.Master(管理)組件 　　a.kube-apiserver 　　b.kube-controller-manager 　　c.kube-scheduler 　　d.

K8s基本概念入門

狀態 啟動 一句話 應用更新 一個 基本概念 而且 多個項目 。。 序言 沒等到風來，綿綿小雨，所以寫個隨筆，聊聊k8s的基本概念。 k8s是一個編排容器的工具，其實也是管理應用的全生命周期的一個工具，從創建應用，應用的部署，應用提供服務，擴容縮容應用，

k8s基本概念

最近在看《Kubernates權威指南》，寫的確實好，能讓你對各種概念有個詳細的瞭解。 1、節點的概念 k8s叢集有兩類節點：Master節點 與 Node節點（非Master）。 Master節點：是叢集控制節點，是叢集的大腦。其上面會有四個關鍵的程序： k

Kubernetes學習筆記——k8s基本概念初探

啥是kubernetes？ 眾所周知，kubernetes(以下簡稱k8s)是google基於Blog進行改進後，開源出來的一款“容器管理應用”。由於近幾年來容器技術的火爆，許許多多的服務都不會直接部署在linux主機或各大雲廠商的虛擬機器上；利用Docker，將每個服務做

K8S基本概念視訊教學學習筆記

K8S基本概念-視訊教學-學習筆記 Rancher官方免費培訓視訊網址： 視訊時長：56分鐘 目錄： 1、配置Rancher和Kubernetes 2、K8S CLI: kubectl使用 3、容器組Pods 4、部署應用Deplotments 5、服務Servic

k8s 集群基本概念<轉>

agen pro point 更新 host 規模 repl 網絡命令 nta k8s 集群基本概念 轉《http://www.cnblogs.com/chris-cp/p/5766153.html》 一、概述： 　　kubernetes是google開源的容器集群管

k8s基本物件概念

基本物件     Pod         Pod是最小部署單元，一個Pod由一個或多個容器組成，Pod中容器共享儲存和網路，在同一臺Docker主機上執行。     Service         Service一個應用服務抽象，定義了Pod邏輯集合和訪問這個Pod集

k8s 叢集基本概念

一、概述： 　　kubernetes是google開源的容器叢集管理系統，提供應用部署、維護、擴充套件機制等功能，利用kubernetes能方便管理跨叢集執行容器化的應用，簡稱：k8s（k與s之間有8個字母） 二、基本概念 　　Pod：若干相關容器的組合，Pod

8 分鐘入門 K8s | 詳解容器基本概念

作者| 阿里巴巴高階開發工程師 傅偉 一、容器與映象 什麼是容器？ 在介紹容器的具體概念之前，先簡單回顧一下作業系統是如何管理程序

ECMAScript基本概念

fin tro ren pro ima ring 變量 調用 fine 1.數據類型 基本數據類型（簡單類型）：Undefined 、Null、String、Boolean、Number 復雜數據類型:Object（和面向對象裏說的類有點相似） 2.變量命名規則 區

ActiveMq的基本概念

要求 更新 它的 高性能 將不 程序 一個 目的 性能 1) 隊列管理器 隊列管理器是MQ系統中最上層的一個概念，由它為我們提供基於隊列的消息服務。 2) 消息 在MQ中，消息分為兩種類型，非永久性(non-persistent)消息和永久性(persistent)消息，非

【Spark深入學習-11】Spark基本概念和運行模式

nmf 磁盤 大數據平臺 並不是 鼠標 .cn 管理系統 大型數據集 spa ----本節內容------- 1.大數據基礎 1.1大數據平臺基本框架 1.2學習大數據的基礎 1.3學習Spark的Hadoop基礎 2.Hadoop生態基本介紹 2.1

MySQL基本概念以及簡單操作

software 倉庫 必須 key 不能 即使 同時 databases ecif 一、MySQL 　　MySQL是一個關系型數據庫管理系統，由瑞典MySQL AB 公司開發，目前屬於Oracle 旗下產品。MySQL 是最流行的關系型數據庫管理系統之一，在 WEB

一、網絡的基本概念

網絡基礎、osi七層協議、tcp三次握手、四次斷開1.1、網絡組成組件 一般來說，兩臺或以上計算機使用任意介質(電纜、光纖或無線電波)、任意網絡(TCP/UDP、NetBEUI或IPX/SPX)來進行連接，並進行資源共享及通信，就可以稱為計算機網絡。網絡協議是網絡上建立通信及傳輸數據的雙方必須遵守的通信標準

Oracle RAC基本概念

特定 遷移 解決方案 開發人員 安裝配置 獲得 情況 網格 play 　　原文鏈接：http://tech.it168.com/a2012/0814/1384/000001384756_all.shtml 　　不同的集群產品都有自己的特點，RAC的特點包括如下幾點： 　　·

Linux 02 Linux基本概念及操作

調用 manual 如何 滾動 示例 函數 script 部分 ctrl+ 基本echo "hello word" 輸出 hello wordtouch file 創建文件名為file 常用快捷鍵TAB：在忘記命令時，可以用來補全命令Ctrl+c：強制終止