一.Replicaset控制器1.建立控制器[rootmaster ~]# kubectl create deployment webcluster --image myapp:v1 --dry-runclient -o yaml repset.yml [rootmaster ~]# vim repset.yml apiVersion: apps/v1 kind: ReplicaSet metadata: labels: app: webcluster name: webcluster spec: replicas: 2 selector: matchLabels: app: webcluster # strategy: {} template: metadata: labels: app: webcluster spec: containers: - image: myapp:v1 name: myapp [rootmaster ~]# kubectl apply -f repset.yml replicaset.apps/webcluster created #打开一个新的shell [rootmaster ~]# watch -n 1 kubectl get pods --show-labels [rootmaster ~]# kubectl scale replicaset webcluster --replicas 4 replicaset.apps/webcluster scaled [rootmaster ~]# kubectl scale replicaset webcluster --replicas 2 replicaset.apps/webcluster scaled [rootmaster ~]# kubectl scale replicaset webcluster --replicas 0 replicaset.apps/webcluster scaled [rootmaster ~]#2.测试功能[rootmaster controler]# vim repset.yml 。。。。 spec: replicas: 4 。。。。 [rootmaster controler]# kubectl apply -f repset.yml [rootmaster ~]# watch -n 1 kubectl get pods --show-labels Every 1.0s: kubectl get pods --show-labels master: Tue Aug 25 22:01:08 2026 NAME READY STATUS RESTARTS AGE LABELS webcluster-6m6mg 1/1 Running 0 2m21s appwebcluster webcluster-dvk76 1/1 Running 0 107s appwebcluster webcluster-srchq 1/1 Running 0 2m21s appwebcluster webcluster-x4x6l 1/1 Running 0 107s appwebcluster二.deployment1.监控[rootmaster ~]# watch -n 1 kubectl get pods --show-labels;echo ;kubectl get replicasets.apps Every 1.0s: kubectl get pods --show-labels;echo ;kubectl get replicasets.apps master: Tue Aug 25 22:02:18 2026 NAME READY STATUS RESTARTS AGE LABELS webcluster-6m6mg 1/1 Running 0 3m31s appwebcluster webcluster-dvk76 1/1 Running 0 2m57s appwebcluster webcluster-srchq 1/1 Running 0 3m31s appwebcluster webcluster-x4x6l 1/1 Running 0 2m57s appwebcluster NAME DESIRED CURRENT READY AGE webcluster 4 4 4 3m31s2.建立deployment控制器[rootmaster ~]# kubectl create deployment webcluster --image myapp:v1 --dry-runclient -o yaml dep.yml [rootmaster ~]# vim dep.yml apiVersion: apps/v1 kind: Deployment metadata: labels: app: webcluster name: webcluster spec: minReadySeconds: 5 replicas: 2 selector: matchLabels: app: webcluster # strategy: {} template: metadata: labels: app: webcluster spec: containers: - image: myapp:v1 name: myapp # resources: {} [rootmaster ~]# kubectl apply -f dep.yml deployment.apps/webcluster created #监控部分显示效果 Every 1.0s: kubectl get pods --show-labels;echo ;kubectl get replicasets.apps master: Tue Aug 25 22:04:46 2026 NAME READY STATUS RESTARTS AGE LABELS webcluster-6m6mg 1/1 Running 0 5m59s appwebcluster webcluster-srchq 1/1 Running 0 5m59s appwebcluster NAME DESIRED CURRENT READY AGE webcluster 2 2 2 5m59s [rootmaster ~]# kubectl expose deployment webcluster --port 80 --target-port 80 Error from server (AlreadyExists): services webcluster already exists [rootmaster ~]# kubectl describe services webcluster Name: webcluster Namespace: default Labels: appwebcluster Annotations: none Selector: appwebcluster Type: NodePort IP Family Policy: SingleStack IP Families: IPv4 IP: 10.105.1.164 IPs: 10.105.1.164 Port: unset 80/TCP TargetPort: 80/TCP NodePort: unset 32416/TCP Endpoints: 10.244.1.20:80,10.244.2.18:80 Session Affinity: None External Traffic Policy: Cluster Internal Traffic Policy: Cluster Events: none [rootmaster ~]# curl 10.105.1.164 Hello MyApp | Version: v1 | a hrefhostname.htmlPod Name/a3.升级和回滚[rootmaster ~]# vim dep.yml 。。。。 spec: minReadySeconds: 5 replicas: 2 selector: matchLabels: app: webcluster # strategy: {} template: metadata: labels: app: webcluster spec: containers: - image: myapp:v2 #升级为版本2 name: myapp 。。。。 [rootmaster ~]# kubectl apply -f dep.yml deployment.apps/webcluster configured [rootmaster ~]# curl 10.105.1.164 Hello MyApp | Version: v2 | a hrefhostname.htmlPod Name/a [rootmaster ~]# vim dep.yml 。。。。 spec: minReadySeconds: 5 replicas: 2 selector: matchLabels: app: webcluster # strategy: {} template: metadata: labels: app: webcluster spec: containers: - image: myapp:v1 #回滚为版本1 name: myapp 。。。。 [rootmaster ~]# kubectl apply -f dep.yml deployment.apps/webcluster configured [rootmaster ~]# curl 10.105.1.164 Hello MyApp | Version: v2 | a hrefhostname.htmlPod Name/a [rootmaster ~]# curl 10.105.1.164 Hello MyApp | Version: v1 | a hrefhostname.htmlPod Name/a三.版本更新管理及优化[rootmaster ~]# vim dep.yml spec: minReadySeconds: 5 replicas: 6 #把pod数量设定为6方便观察 selector: [rootmaster ~]# kubectl apply -f dep.yml deployment.apps/webcluster configured1.查看更新策略信息[rootmaster ~]# kubectl describe deployments.apps webcluster Name: webcluster Namespace: default CreationTimestamp: Tue, 25 Aug 2026 22:03:30 0800 Labels: appwebcluster Annotations: deployment.kubernetes.io/revision: 3 Selector: appwebcluster Replicas: 6 desired | 6 updated | 6 total | 6 available | 0 unavailable StrategyType: RollingUpdate MinReadySeconds: 5 RollingUpdateStrategy: 25% max unavailable, 25% max surge Pod Template: Labels: appwebcluster Containers: myapp: Image: myapp:v1 Port: none Host Port: none Environment: none Mounts: none Volumes: none Node-Selectors: none Tolerations: none Conditions: Type Status Reason ---- ------ ------ Progressing True NewReplicaSetAvailable Available True MinimumReplicasAvailable OldReplicaSets: webcluster-6c8b4bb9d7 (0/0 replicas created) NewReplicaSet: webcluster (6/6 replicas created) Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal ScalingReplicaSet 8m5s deployment-controller Scaled down replica set webcluster from 4 to 2 Normal ScalingReplicaSet 4m1s deployment-controller Scaled up replica set webcluster-6c8b4bb9d7 from 0 to 1 Normal ScalingReplicaSet 3m56s deployment-controller Scaled down replica set webcluster from 2 to 1 Normal ScalingReplicaSet 3m56s deployment-controller Scaled up replica set webcluster-6c8b4bb9d7 from 1 to 2 Normal ScalingReplicaSet 3m50s deployment-controller Scaled down replica set webcluster from 1 to 0 Normal ScalingReplicaSet 3m27s deployment-controller Scaled up replica set webcluster from 0 to 1 Normal ScalingReplicaSet 3m21s deployment-controller Scaled down replica set webcluster-6c8b4bb9d7 from 2 to 1 Normal ScalingReplicaSet 3m21s deployment-controller Scaled up replica set webcluster from 1 to 2 Normal ScalingReplicaSet 3m15s deployment-controller Scaled down replica set webcluster-6c8b4bb9d7 from 1 to 0 Normal ScalingReplicaSet 64s deployment-controller (combined from similar events): Scaled up replica set webcluster from 2 to 62.设定更新策略[rootmaster ~]# vim dep.yml spec: minReadySeconds: 5 replicas: 6 selector: matchLabels: app: webcluster strategy: rollingUpdate: maxSurge: 1 #更新时pod数量最多比期望值多一个 maxUnavailable: 0 #不能使用pod数量比期望值数量多0 template: metadata: labels: app: webcluster spec: containers: - image: myapp:v1 name: myapp [rootmaster ~]# kubectl apply -f dep.yml deployment.apps/webcluster configured3.更新暂停和恢复[rootmaster ~]# kubectl rollout history deployment webcluster deployment.apps/webcluster REVISION CHANGE-CAUSE 2 none 3 none [rootmaster ~]# kubectl rollout pause deployment webcluster deployment.apps/webcluster paused [rootmaster ~]# vim dep.yml 。。。 containers: - image: myapp:v2 name: myapp 。。。 [rootmaster ~]# kubectl apply -f dep.yml deployment.apps/webcluster configured [rootmaster ~]# kubectl rollout history deployment webcluster deployment.apps/webcluster REVISION CHANGE-CAUSE 3 none 4 none [rootmaster ~]# kubectl rollout resume deployment webcluster deployment.apps/webcluster resumed [rootmaster ~]# kubectl rollout history deployment webcluster deployment.apps/webcluster REVISION CHANGE-CAUSE 3 none 4 none四.DaemonSet[rootmaster controler]# kubectl create deployment daemonset --image myapp:v1 --dry-runclient -o yaml daemonset.yml [rootmaster controler]# vim daemonset.yml apiVersion: apps/v1 kind: DaemonSet metadata: labels: app: daemonset name: daemonset spec: selector: matchLabels: app: daemonset template: metadata: labels: app: daemonset spec: containers: - image: myapp:v1 name: myapp #另外开启一个主机node3并设定在初始化集群时的所有设定确保所有服务的开启 #在master中重新生成集群主机注册时需要的token [rootmaster ~]# kubeadm token create --print-join-command kubeadm join 192.168.106.181:6443 --token ozlv7n.5bm7z0b1msapxc3t --discovery-token-ca-cert-hash sha256:9cb037f40d64a5c3c7f6f6019f4a56cf8096f9e28a19fb9d08990d7d11ff9008 [rootmaster ~]# [rootnode3 ~]# kubeadm join 192.168.106.181:6443 --token ozlv7n.5bm7z0b1msapxc3t --discovery-token-ca-cert-hash sha256:9cb037f40d64a5c3c7f6f6019f4a56cf8096f9e28a19fb9d08990d7d11ff9008 --cri-socket unix:///var/run/cri-dockerd.sock #当node3加入集群后会在node3中立即群星指定的pod其原因是因为运行了daemonset #可以在master中观察pod的状态五.Job控制器[rootmaster ~]# kubectl create job testjob --image busybox job.batch/testjob created [rootmaster ~]# kubectl create job testjob --image busybox --dry-runclient -o yaml apiVersion: batch/v1 kind: Job metadata: name: testjob spec: template: metadata: {} spec: containers: - image: busybox name: testjob resources: {} restartPolicy: Never status: {} [rootmaster ~]# kubectl create job testjob --image busybox --dry-runclient -o yaml testjob.yaml [rootmaster ~]# vim testjob.yaml apiVersion: batch/v1 kind: Job metadata: name: testjob spec: completions: 6 parallelism: 2 backoffLimit: 4 template: spec: containers: - image: busybox name: testjob command: [/bin/sh, -c] args: - | echo this is testjob message sleep 10 restartPolicy: Never [rootmaster ~]# kubectl apply -f testjob.yaml job.batch/testjob created [rootmaster ~]# kubectl logs testjob-v5j94 this is testjob message六.Cronjob控制器[rootmaster ~]# kubectl delete -f testjob.yaml job.batch testjob deleted from default namespace [rootmaster ~]# cp testjob.yaml crontabjob.yml [rootmaster ~]# vim crontabjob.yml apiVersion: batch/v1 kind: CronJob metadata: name: cronjob spec: schedule: * * * * * jobTemplate: spec: template: spec: restartPolicy: Never # 注意 P 是大写 containers: - image: busybox name: cronjob command: [/bin/sh, -c] args: - | echo this is testjob message sleep 10 [rootmaster ~]# kubectl apply -f crontabjob.yml cronjob.batch/cronjob created