控制器含義解釋

空調(diào)遙控器知道吧ReplicationController: ReplicationController確保在任何時(shí)候都運(yùn)行指定數(shù)量的pod副本。換句話說，一個(gè)ReplicationController確保一個(gè)pod或一組同類的pod總是處于可用狀態(tài)。ReplicaSet: ReplicaSet的目的是維護(hù)在任何給定時(shí)間運(yùn)行的一組穩(wěn)定的pod副本。因此，它通常用于保證指定數(shù)量的相同pod的可用性。Deployments: 部署針對Pods和ReplicaSets提供了宣告式的更新。StatefulSets: StatefulSet常用于管理有狀態(tài)的應(yīng)用。DaemonSet: 它是確保所有的節(jié)點(diǎn)或一些節(jié)點(diǎn)都運(yùn)行一個(gè)Pod的復(fù)本。

pod的標(biāo)簽與注釋

標(biāo)簽就是名字的意思
kubectl run httpd \
--image=httpd:2.4 \
--replicas=1 \
--labels="ver=2,env=prod"查看標(biāo)簽 
kubectl get deployment --show-labelskubectl label deployments httpd "canary=true"
kubectl get deployment -L canary
移除 
kubectl get deployment -L canary
顯示標(biāo)簽 kubectl get pods --show-labels選擇標(biāo)簽為某個(gè)值
kubectl get pod --selector="ver=2"標(biāo)簽是抓取pod的唯一依據(jù)

ReplicaController

管理它自己管理的pod數(shù)量保持一致[root@k8s-01 chapter04]# cat web-rc.yaml 
apiVersion: v1
kind: ReplicationController
metadata:name: web
spec:replicas: 3selector:app: nginxtemplate:metadata:labels:app: nginxspec:containers:- name: nginximage: nginxports:- containerPort: 80[root@k8s-01 chapter04]# kubectl create -f web-rc.yaml 
replicationcontroller/web created
[root@k8s-01 chapter04]# kubectl get pod
NAME                    READY   STATUS              RESTARTS   AGE
httpd                   1/1     Running             0          22m
httpd-1                 1/1     Running             0          21m
nginx-97499b967-jzxwg   1/1     Running             0          14h
web-5bq9k               0/1     ContainerCreating   0          4s
web-rvbmm               0/1     ContainerCreating   0          4s
web-x6wxd               0/1     ContainerCreating   0          4s
[root@k8s-01 chapter04]# kubectl  get rc
NAME   DESIRED   CURRENT   READY   AGE
web    3         3         0       14s
[root@k8s-01 chapter04]# kubectl get replicationController
NAME   DESIRED   CURRENT   READY   AGE
web    3         3         1       27s如果刪除一個(gè)pod ，會自己新增一個(gè)pod
kubectl delete pod/web-x6wxd新增一個(gè)標(biāo)簽看看
[root@k8s-01 chapter04]# kubectl get pod --show-labels
NAME                    READY   STATUS    RESTARTS   AGE     LABELS
nginx-97499b967-jzxwg   1/1     Running   0          14h     app=nginx,pod-template-hash=97499b967
web-rftd7               1/1     Running   0          4m16s   app=nginx
web-rvbmm               1/1     Running   0          7m35s   app=nginx
web-x6wxd               1/1     Running   0          7m35s   app=nginx[root@k8s-01 chapter04]# kubectl label pod web-rftd7 type=special
pod/web-rftd7 labeled
[root@k8s-01 chapter04]# kubectl get pod --show-labels
NAME                    READY   STATUS    RESTARTS   AGE     LABELS
nginx-97499b967-jzxwg   1/1     Running   0          14h     app=nginx,pod-template-hash=97499b967
web-rftd7               1/1     Running   0          5m20s   app=nginx,type=special
web-rvbmm               1/1     Running   0          8m39s   app=nginx
web-x6wxd               1/1     Running   0          8m39s   app=nginx覆蓋過去
kubectl label pod web-rftd7 app=nginx1 --overwrite添加pod的標(biāo)簽
# kubectl label pod web-z8stj type=special更改pod的標(biāo)簽
# kubectl label pod web-z8stj app=foo --overwrite再次列出pod
# kubectl get pods –L app修改rc的數(shù)量為2個(gè)
[root@k8s-01 chapter04]# kubectl get rc
NAME   DESIRED   CURRENT   READY   AGE
web    3         3         3       17m
[root@k8s-01 chapter04]# kubectl edit rc web
replicationcontroller/web edited
[root@k8s-01 chapter04]# kubectl get rc
NAME   DESIRED   CURRENT   READY   AGE
web    2         2         2       18m修改里面的數(shù)量為2 個(gè)水平擴(kuò)縮容
[root@k8s-01 chapter04]# kubectl scale rc web --replicas=6
replicationcontroller/web scaled
[root@k8s-01 chapter04]# kubectl get pod
NAME                    READY   STATUS              RESTARTS   AGE
nginx-97499b967-jzxwg   1/1     Running             0          14h
web-fhg2l               0/1     ContainerCreating   0          4s
web-nsxsh               0/1     ContainerCreating   0          4s
web-pcwkz               0/1     ContainerCreating   0          4s
web-rvbmm               1/1     Running             0          19m
web-vj48d               0/1     ContainerCreating   0          4s
web-x6wxd               1/1     Running             0          19mkubectl delete rc web ,刪除rcRC (ReplicaController) 通過標(biāo)簽來控制pod的，改變pod的標(biāo)簽，pod會進(jìn)行變化

ReplicaSet

針對rc而言，選擇更加靈活kubectl describe rs[root@k8s-01 chapter04]# cat web-replicaset.yaml 
apiVersion: apps/v1
kind: ReplicaSet
metadata:name: web
spec:replicas: 3selector:matchLabels:app: nginxtemplate:metadata:labels:app: nginxspec:containers:- name: nginximage: nginx生產(chǎn)環(huán)境用rs多些

Deployments

Deployment為Pods和ReplicaSets提供聲明式的更新。
在部署中描述一個(gè)期望的狀態(tài)，部署控制器以某個(gè)控制的速率改變實(shí)際的狀態(tài)到期望的狀態(tài)控制更新的節(jié)奏和速率[root@k8s-01 chapter04]# cat nginx-deployment.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:name: nginx-deploymentlabels:app: nginx
spec:replicas: 3selector:matchLabels:app: nginxtemplate:metadata:labels:app: nginxspec:containers:- name: nginximage: nginx:1.7.9ports:- containerPort: 80創(chuàng)建
# kubectl apply –f nginx-deployment.yaml查看部署
# kubectl get deployment查看部署的狀態(tài)
# kubectl rollout status deployment.v1.apps/nginx-deployment查看通過部署創(chuàng)建的rs
# kubectl get rs查看pod自動產(chǎn)生的labels
# kubectl get pods –show-labels更新nginx:1.7.9為nginx:1.9.1
# kubectl –record deployment.apps/nginx-deployment set image deployment.v1.apps/nginx-deployment nginx=nginx:1.9.1
或者：
# kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1 –record
或者：
# kubectl edit deployment.v1.apps/nginx-deployment查看更新的狀態(tài)
# kubectl rollout status deployment.v1.apps/nginx-deployment通過以下命令查看部署
# kubectl get deployment查看部署的rs
# kubectl get rs查看新的pods
# kubectl get pods查看部署的詳情
# kubectl describe deployments回滾部署
更新一個(gè)不存在的鏡像
# kubectl set image deployment.v1.apps/nginx-deployment nginx=nginx:1.91 –record=true通過以下命令查看更新卡住了
# kubectl rollout status deployment.v1.apps/nginx-deployment查看部署的rs
# kubectl get rs查看部署的pods
# kubectl get pods查看部署的描述信息
# kubectl describe deployment查看部署的版本
# kubectl rollout history deployment.v1.apps/nginx-deployment查看每個(gè)版本的詳情
# kubectl rollout history deployment.v1.apps/nginx-deployment –revision=2回退到先前的版本
# kubectl rollout undo deployment.v1.apps/nginx-deployment回退到特定的版本
# kubectl rollout undo deployment.v1.apps/nginx-deployment --to-revision=2檢查回退是否成功
# kubectl get deployment nginx-deployment部署的擴(kuò)容
擴(kuò)容副本數(shù)量為10
# kubectl scale deployment.v1.apps/nginx-deployment --replicas=10如果啟用了水平的pod自動擴(kuò)容可以執(zhí)行如下：
# kubectl autoscale deployment.v1.apps/nginx-deployment --min=10 --max=15 --cpu-percent=80擴(kuò)容的比例和刻度
確保部署的10個(gè)復(fù)本處于運(yùn)行
# kubectl get deploy更新一個(gè)不存在的鏡像，并查看結(jié)果
# kubectl set image deployment.v1.apps/nginx-deployment nginx=nginx:sometag
# kubectl get rs更新復(fù)本的數(shù)量為15個(gè)，再次查看結(jié)果,然后刪除本次部署
#  kubectl scale deployment.v1.apps/nginx-deployment --replicas=15
# kubectl get deployment
# kubectl get rs
# kubectl delete deploy nginx-deployment暫停和繼續(xù)部署
創(chuàng)建部署
# kubectl create –f nginx-deployment.yaml暫停更新
# kubectl rollout pause deployment.v1.apps/nginx-deployment更新鏡像
# kubectl set image deployment.v1.apps/nginx-deployment nginx=nginx:1.9.1查看是否有新的更新開始
# kubectl rollout history deployment.v1.apps/nginx-deployment恢復(fù)部署
# kubectl rollout resume deployment.v1.apps/nginx-deployment

DaemonSet

使用DaemonSet在每個(gè)節(jié)點(diǎn)上運(yùn)行一個(gè)pod
DaemonSet確保創(chuàng)建盡可能多的pod,并將每個(gè)pod部署到自己的節(jié)點(diǎn)上。使用DaemonSet僅在特定的節(jié)點(diǎn)上運(yùn)行Pods
這可以通過在pod模板中指定node-selector屬性來完成的，它是DaemonSet定義的一部分[root@k8s-01 chapter04]# cat ssd-monitor-daemonset.yaml 
apiVersion: apps/v1
kind: DaemonSet
metadata:name: ssd-monitor
spec:selector:matchLabels:app: ssd-monitortemplate:metadata:labels:app: ssd-monitorspec:nodeSelector:disk: ssdcontainers:- name: mainimage: luksa/ssd-monitor[root@k8s-01 chapter04]# kubectl get pod -o wide
NAME                    READY   STATUS    RESTARTS   AGE   IP           NODE     NOMINATED NODE   READINESS GATES
nginx-97499b967-jzxwg   1/1     Running   0          16h   10.244.1.2   k8s-02   <none>           <none>打標(biāo)簽
kubectl label node k8s-02 disk=ssdkubectl get ds
kubectl get pods打完標(biāo)簽后指哪打哪

Job

這種是運(yùn)行一次，直到完成在Job完成后，它并不會刪除Pod，允許我們可以查看它的日志在Job中運(yùn)行多個(gè)Pod實(shí)例
Job可以配置為創(chuàng)建多個(gè)Pod實(shí)例，依并行或有序的方式運(yùn)行它們。按順序來運(yùn)行Job
如果需要一個(gè)job運(yùn)行多次，可以將completions設(shè)置為希望job的Pod運(yùn)行多次。
配置請參考文件：multi-completion-batch-job.yaml以并行的方式運(yùn)行job pods.
如果讓job并行運(yùn)行多個(gè)pods，可以使用parallelism指定并運(yùn)行pod的數(shù)量。
配置請參考文件：multi-completion-batch-job2.yaml限制Job pod的完成時(shí)間
通過設(shè)置activedeadlinesecond屬性 [root@k8s-01 chapter04]# cat multi-completion-batch-job.yaml 
apiVersion: batch/v1
kind: Job
metadata:name: multi-completion-batch-job
spec:completions: 5template:metadata:labels:app: batch-jobspec:restartPolicy: OnFailurecontainers:- name: mainimage: luksa/batch-job
[root@k8s-01 chapter04]# cat multi-completion-batch-job2.yaml 
apiVersion: batch/v1
kind: Job
metadata:name: multi-completion-batch-job2
spec:completions: 5parallelism: 2template:metadata:labels:app: batch-jobspec:restartPolicy: OnFailurecontainers:- name: mainimage: luksa/batch-job

Cronjob

這個(gè)是定時(shí)計(jì)劃任務(wù)，周期性的[root@k8s-01 chapter04]# cat batch-job-every-fifteen-minutes.yaml 
apiVersion: batch/v1beta1
# API group的版本是v1beat1,這里不要寫錯(cuò)
kind: CronJob
metadata:name: batch-job-every-fifteen-minutes
spec:
# 該任務(wù)將會在每小時(shí)的0，15，30，45分運(yùn)行schedule: "0,15,30,45 * * * *"jobTemplate:spec:template:metadata:labels:app: periodic-batch-job-every-fifteen-minutesspec:restartPolicy: OnFailurecontainers:- name: mainimage: luksa/batch-job
[root@k8s-01 chapter04]# cat cronjob.yaml 
apiVersion: batch/v1beta1
kind: CronJob
metadata:name: hello
spec:schedule: "*/1 * * * *"jobTemplate:spec:template:spec:containers:- name: helloimage: busyboxargs:- /bin/sh- -c- date; echo Hello from the kubernetes clusterrestartPolicy: OnFailure使用以下命令獲取它的狀態(tài)
# kubectl get cronjob hello也可以通過以下命令獲取它的狀態(tài)
# kubectl get jobs --watch可以通過以下命令查看上次調(diào)度的時(shí)間
# kubectl get conrjob hello刪除cronjob
# kubectl delete cronjob hello

參考文檔

https://edu.csdn.net/course/detail/27762?spm=1003.2449.3001.8295.2