k8s 常用工作负载控制器（Deployment、DaemonSet、Job、CronJob）(1)

感受：

其实我投简历的时候，都不太敢投递阿里。因为在阿里一面前已经过了字节的三次面试，投阿里的简历一直没被捞，所以以为简历就挂了。

特别感谢一面的面试官捞了我，给了我机会，同时也认可我的努力和态度。对比我的面经和其他大佬的面经，自己真的是运气好。别人8成实力，我可能8成运气。所以对我而言，我要继续加倍努力，弥补自己技术上的不足，以及与科班大佬们基础上的差距。希望自己能继续保持学习的热情，继续努力走下去。

也祝愿各位同学，都能找到自己心动的offer。

分享我在这次面试前所做的准备（刷题复习资料以及一些大佬们的学习笔记和学习路线），都已经整理成了电子文档

本文已被CODING开源项目：【一线大厂Java面试题解析+核心总结学习笔记+最新讲解视频+实战项目源码】收录

需要这份系统化的资料的朋友，可以点击这里获取

[root@master test]# cat test.yml

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

namespace: default

spec:

replicas: 3

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

• name: web

image: 1314444/httpd:v0.1

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f test.yml

deployment.apps/web created

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-c45fdccd9-shmdj 1/1 Running 0 2m1s

web-c45fdccd9-xthqz 1/1 Running 0 2m1s

web-c45fdccd9-ztzk7 1/1 Running 0 2m1s

//更新

[root@master test]# cat test.yml

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

namespace: default

spec:

replicas: 4

strategy:

rollingUpdate:

maxSurge: 25% #默认便是25%，所以可以不用写

maxUnavailable: 25% #默认便是25%，所以可以不用写

type: RollingUpdate

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

• name: web

image: 1314444/httpd:v0.2

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f test.yml

deployment.apps/web configured

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-c45fdccd9-bjt6r 1/1 Running 0 2s

web-c45fdccd9-shmdj 1/1 Running 0 3m

web-c45fdccd9-xthqz 1/1 Running 0 3m

web-c45fdccd9-ztzk7 1/1 Running 0 3m

rollingUpdate 有四舍五入的功能，是根据副本数量而决定

-------双数副本数量-------

[root@master test]# cat test.yml

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

namespace: default

spec:

replicas: 4

strategy:

rollingUpdate:

maxSurge: 50%

maxUnavailable: 50%

type: RollingUpdate

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

• name: web

image: 1314444/httpd:v0.1

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f test.yml

deployment.apps/web configured

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-865bffff44-ft6xg 1/1 Running 0 3s

web-865bffff44-gdjdj 1/1 Running 0 3s

web-865bffff44-rgwv6 1/1 Running 0 3s

web-865bffff44-whdhh 1/1 Running 0 3s

web-c45fdccd9-bjt6r 1/1 Terminating 0 9m11s

web-c45fdccd9-shmdj 1/1 Terminating 0 12m

web-c45fdccd9-xthqz 1/1 Terminating 0 12m

web-c45fdccd9-ztzk7 1/1 Terminating 0 12m

-------副本数量单数-------

[root@master test]# cat test.yml

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

namespace: default

spec:

replicas: 5

strategy:

rollingUpdate:

maxSurge: 50%

maxUnavailable: 50%

type: RollingUpdate

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

• name: web

image: 1314444/httpd:v0.2

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f test.yml

deployment.apps/web configured

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-865bffff44-ft6xg 1/1 Terminating 0 4m4s

web-865bffff44-gdjdj 1/1 Terminating 0 4m4s

web-865bffff44-nqskm 0/1 Terminating 0 2s

web-865bffff44-rgwv6 1/1 Terminating 0 4m4s

web-865bffff44-whdhh 1/1 Running 0 4m4s

web-c45fdccd9-6s8vr 1/1 Running 0 2s

web-c45fdccd9-jgcgm 0/1 ContainerCreating 0 2s

web-c45fdccd9-qmw2k 0/1 ContainerCreating 0 2s

web-c45fdccd9-wdnvj 0/1 ContainerCreating 0 2s

web-c45fdccd9-zf4mt 1/1 Running 0 2s

-------四舍五入-------

[root@master test]# cat test.yml

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

namespace: default

spec:

replicas: 5

strategy:

rollingUpdate:

maxSurge: 49%

maxUnavailable: 49%

type: RollingUpdate

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

• name: web

image: 1314444/httpd:v0.1

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f test.yml

deployment.apps/web configured

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-865bffff44-89grr 1/1 Running 0 1s

web-865bffff44-d2ggx 0/1 ContainerCreating 0 1s

web-865bffff44-fzg6s 1/1 Running 0 1s

web-865bffff44-sv27k 1/1 Running 0 1s

web-865bffff44-w2jdq 1/1 Running 0 1s

web-c45fdccd9-6s8vr 1/1 Terminating 0 5m20s

web-c45fdccd9-jgcgm 1/1 Terminating 0 5m20s

web-c45fdccd9-qmw2k 1/1 Terminating 0 5m20s

web-c45fdccd9-wdnvj 1/1 Terminating 0 5m20s

web-c45fdccd9-zf4mt 1/1 Terminating 0 5m20s

水平扩缩容

水平扩缩容(启动多实例,提高并发)

• 修改yaml里replicas值，再apply

• kubectl scale deployment web --replicas=10

注: replicas参数控制Pod副本数量

[root@master test]# cat test.yml

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

namespace: default

spec:

replicas: 3 #副本数量

strategy:

rollingUpdate:

maxSurge: 49%

maxUnavailable: 49%

type: RollingUpdate

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

• name: web

image: 1314444/httpd:v0.2

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f test.yml

deployment.apps/web configured

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-865bffff44-89grr 1/1 Terminating 0 8m35s

web-865bffff44-d2ggx 1/1 Terminating 0 8m35s

web-865bffff44-fzg6s 1/1 Running 0 8m35s

web-865bffff44-sv27k 1/1 Running 0 8m35s

web-865bffff44-w2jdq 1/1 Running 0 8m35s

Deployment 回滚

回滚（发布失败恢复正常版本)

kubectl rollout history deployment/web #查看历史发布版本

kubectl rollout undo deployment/web #回滚上一个版本

kubectl rollout undo deployment/web --to-revision=2 #回滚历史指定版本

注:回滚是重新部署某一次部署时的状态，即当时版本所有配置

//查看历史发布版本

[root@master test]# kubectl rollout history deploy/web

deployment.apps/web

REVISION CHANGE-CAUSE

3

4

//回滚上一个版本

[root@master test]# cat test.yml

apiVersion: apps/v1

kind: Deployment

metadata:

name: web

namespace: default

spec:

replicas: 3

strategy:

rollingUpdate:

maxSurge: 49%

maxUnavailable: 49%

type: RollingUpdate

selector:

matchLabels:

app: web

template:

metadata:

labels:

app: web

spec:

containers:

• name: web

image: 1314444/httpd:v0.1

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f test.yml

deployment.apps/web configured

[root@master test]# kubectl get pod -o wide

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES

web-865bffff44-hpqw9 1/1 Running 0 67s 10.244.1.173 node1

web-865bffff44-nwbx4 1/1 Running 0 67s 10.244.1.174 node1

web-865bffff44-w9568 1/1 Running 0 67s 10.244.1.172 node1

[root@master test]# curl 10.244.1.174

test page on jjyy

[root@master test]# kubectl rollout undo deploy/web

deployment.apps/web rolled back

[root@master test]# kubectl get pod -o wide

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES

web-865bffff44-hpqw9 1/1 Terminating 0 67s 10.244.1.173 node1

web-865bffff44-nwbx4 1/1 Terminating 0 67s 10.244.1.174 node1

web-865bffff44-w9568 1/1 Terminating 0 67s 10.244.1.172 node1

web-c45fdccd9-8cm86 1/1 Running 0 8s 10.244.1.175 node1

web-c45fdccd9-bhndv 1/1 Running 0 8s 10.244.1.176 node1

web-c45fdccd9-k8c7b 1/1 Running 0 8s 10.244.1.177 node1

[root@master test]# curl 10.244.1.174

test page on jjyy

[root@master test]# curl 10.244.1.177

test page on 666

Deployment 下线

• kubectl delete deploy/web

• kubectl delete svc/web

//删除(推荐使用)

[root@master test]# kubectl delete -f test.yml

deployment.apps “web” deleted

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-865bffff44-9sbnl 1/1 Terminating 0 5m26s

web-865bffff44-b44nb 1/1 Terminating 0 5m26s

web-865bffff44-tvzvw 1/1 Terminating 0 5m26s

Deployment ReplicaSet

ReplicaSet控制器用途

• Pod副本数量管理，不断对比当前Pod数量与期望Pod数量

• Deployment每次发布都会创建一个RS作为记录，用于实现回滚

• 默认为一个Pod数量

[root@master test]# kubectl get pod

NAME READY STATUS RESTARTS AGE

web-865bffff44-49zns 1/1 Running 0 42s

web-865bffff44-7g7b5 1/1 Running 0 42s

web-865bffff44-rq59f 1/1 Running 0 42s

[root@master test]# kubectl get rs #查看RS记录（根据副本的多少来判断）

NAME DESIRED CURRENT READY AGE

web-865bffff44 3 3 3 3s

[root@master test]# kubectl rollout history deploy web #版本对应RS记录

deployment.apps/web

REVISION CHANGE-CAUSE

1

DaemonSet

---

DaemonSet功能

• 在每一个Node上运行一个Pod

• 新加入的Node也同样会自动运行一个Pod

应用场景

• 网络插件(kube-proxy、calico)、其他Agent

示例:部署一个日志采集程序

[root@master test]# cat daemon.yml

apiVersion: apps/v1

kind: DaemonSet

metadata:

name: filebeat

namespace: kube-system

spec:

selector:

matchLabels:

app: filebeat

template:

metadata:

labels:

app: filebeat

spec:

containers:

• name: log

image: elastic/filebeat:7.16.2

imagePullPolicy: IfNotPresent

[root@master test]# kubectl apply -f daemon.yml

daemonset.apps/filebeat created

[root@master test]# kubectl get pod -n kube-system

NAME READY STATUS RESTARTS AGE

coredns-7f89b7bc75-ptq5m 1/1 Running 14 6d7h

coredns-7f89b7bc75-v6chh 1/1 Running 14 6d7h

etcd-master 1/1 Running 16 6d7h

filebeat-4l848 0/1 ContainerCreating 0 8s #首次拉取镜像有点慢

filebeat-wk9dt 0/1 ContainerCreating 0 8s

kube-apiserver-master 1/1 Running 16 6d7h

kube-controller-manager-master 1/1 Running 16 6d7h

kube-flannel-ds-cchk6 1/1 Running 12 6d6h

kube-flannel-ds-d2wpq 1/1 Running 14 6d6h

kube-flannel-ds-z6f85 1/1 Running 0 160m

kube-proxy-6f99q 1/1 Running 13 6d7h

kube-proxy-9z78l 1/1 Running 11 6d7h

kube-proxy-gz4bs 1/1 Running 16 6d7h

kube-scheduler-master 1/1 Running 16 6d7h

//DaemonSet类型的会在除了master节点以外的所有节点上创建

[root@master test]# kubectl get pod -n kube-system -o wide

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES

coredns-7f89b7bc75-ptq5m 1/1 Running 14 6d7h 10.244.0.38 master

coredns-7f89b7bc75-v6chh 1/1 Running 14 6d7h 10.244.0.39 master

etcd-master 1/1 Running 16 6d7h 192.168.129.250 master

filebeat-4l848 1/1 Running 0 3m5s 10.244.2.59 node2

filebeat-wk9dt 1/1 Running 0 3m5s 10.244.1.183 node1

kube-apiserver-master 1/1 Running 16 6d7h 192.168.129.250 master

kube-controller-manager-master 1/1 Running 16 6d7h 192.168.129.250 master

kube-flannel-ds-cchk6 1/1 Running 12 6d6h 192.168.129.136 node2

kube-flannel-ds-d2wpq 1/1 Running 14 6d6h 192.168.129.250 master

kube-flannel-ds-z6f85 1/1 Running 0 163m 192.168.129.135 node1

kube-proxy-6f99q 1/1 Running 13 6d7h 192.168.129.136 node2

kube-proxy-9z78l 1/1 Running 11 6d7h 192.168.129.135 node1

kube-proxy-gz4bs 1/1 Running 16 6d7h 192.168.129.250 master

kube-scheduler-master 1/1 Running 16 6d7h 192.168.129.250 master

加入新节点

//查看本地节点

[root@master ~]# kubectl get node

NAME STATUS ROLES AGE VERSION

master Ready control-plane,master 6d22h v1.20.0

node1 Ready 6d22h v1.20.0

node2 Ready 6d22h v1.20.0

//加入新的节点

//注释swap分区

[root@master ~]# sed -i.bak ‘/swap/s/^/#/’ /etc/fstab

//关闭防火墙

[root@node3 ~]# systemctl disable --now firewalld

Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service.

Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.

[root@node3 ~]# sed -i ‘s/enforcing/disabled/’ /etc/selinux/config

//重启

[root@node3 ~]# reboot

//配置yum源

[root@node3 ~]# curl -o /etc/yum.repos.d/CentOS-Base.repo https://mirrors.aliyun.com/repo/Centos-8.repo

[root@node3 ~]# sed -i -e ‘/mirrors.cloud.aliyuncs.com/d’ -e ‘/mirrors.aliyuncs.com/d’ /etc/yum.repos.d/CentOS-Base.repo

[root@node3 ~]# yum clean all && yum makecache

//时间同步

[root@node3 ~]# yum -y install chrony

[root@node3 ~]# sed -i ‘s/2.centos.pool.ntp.org/time1.aliyun.com/’ /etc/chrony.conf

[root@node3 ~]# systemctl enable --now chronyd

[root@node3 ~]# date

2021年 12月 25日 星期六 14:51:13 CST

//安装Docker

[root@node3 ~]# yum -y install wget

[root@node3 ~]# wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo

[root@node3 ~]# yum -y install docker-ce

[root@node3 ~]# systemctl enable --now docker

Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /usr/lib/systemd/system/docker.service.

[root@node3 ~]# docker --version

Docker version 20.10.12, build e91ed57

[root@master ~]# ls /etc/docker/

key.json

//镜像加速

[root@master ~]# cat > /etc/docker/daemon.json << EOF

{

“registry-mirrors”: [“https://b9pmyelo.mirror.aliyuncs.com”],

“exec-opts”: [“native.cgroupdriver=systemd”],

“log-driver”: “json-file”,

“log-opts”: {

“max-size”: “100m”

},

“storage-driver”: “overlay2”

}

EOF

//添加kubernetes阿里云YUM软件源

[root@node3 ~]# cat > /etc/yum.repos.d/kubernetes.repo << EOF

[kubernetes]

name=Kubernetes

baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64

enabled=1

gpgcheck=0

repo_gpgcheck=0

gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg

EOF

[root@node3 ~]# yum clean all && yum makecache

//安装kubeadm，kubelet和kubectl,由于版本更新频繁，这里指定版本号部署

[root@node3 ~]# yum install -y kubelet-1.20.0 kubeadm-1.20.0 kubectl-1.20.0

[root@node3 ~]# systemctl enable kubelet

Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /usr/lib/systemd/system/kubelet.service.

[root@node3 ~]# systemctl status kubelet

● kubelet.service - kubelet: The Kubernetes Node Agent

Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)

Drop-In: /usr/lib/systemd/system/kubelet.service.d

└─10-kubeadm.conf

Active: inactive (dead)

//master端做域名解析

[root@master ~]# cat /etc/hosts

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

192.168.129.250 master master.example.com

192.168.129.135 node1 node1.example.com

192.168.129.136 node2 node2.example.com

192.168.129.205 node3 node3.example.com

//做免密登录

[root@master ~]# ssh-copy-id node3

//加入集群

//此时需要通过 kubedam重新生成token

[root@master ~]# token=$(kubeadm token generate)

[root@master ~]# kubeadm token create $token --print-join-command --ttl=0

kubeadm join 192.168.129.250:6443 --token k1m9je.bh5l7nddlw548eva --discovery-token-ca-cert-hash sha256:f6be891c6cd273a9283a6c05ca795811f7350afa2b5072990a294b7070ff9a4f

[root@node3 ~]# kubeadm join 192.168.129.250:6443 --token k1m9je.bh5l7nddlw548eva --discovery-token-ca-cert-hash sha256:f6be891c6cd273a9283a6c05ca795811f7350afa2b5072990a294b7070ff9a4f

[preflight] Running pre-flight checks

[WARNING FileExisting-tc]: tc not found in system path

[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.12. Latest validated version: 19.03

[WARNING Hostname]: hostname “node3” could not be reached

[WARNING Hostname]: hostname “node3”: lookup node3 on 114.114.114.114:53: no such host

[preflight] Reading configuration from the cluster…

[preflight] FYI: You can look at this config file with ‘kubectl -n kube-system get cm kubeadm-config -o yaml’

[kubelet-start] Writing kubelet configuration to file “/var/lib/kubelet/config.yaml”

[kubelet-start] Writing kubelet environment file with flags to file “/var/lib/kubelet/kubeadm-flags.env”

[kubelet-start] Starting the kubelet

[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap…

This node has joined the cluster:

• Certificate signing request was sent to apiserver and a response was received.

复习的面试资料

这些面试全部出自大厂面试真题和面试合集当中，小编已经为大家整理完毕（PDF版）

• 第一部分：Java基础-中级-高级

• 第二部分：开源框架（SSM：Spring+SpringMVC+MyBatis）

• 第三部分：性能调优（JVM+MySQL+Tomcat）

• 第四部分：分布式（限流：ZK+Nginx；缓存：Redis+MongoDB+Memcached；通讯：MQ+kafka）

• 第五部分：微服务（SpringBoot+SpringCloud+Dubbo）

• 第六部分：其他：并发编程+设计模式+数据结构与算法+网络

进阶学习笔记pdf

• Java架构进阶之架构筑基篇（Java基础+并发编程+JVM+MySQL+Tomcat+网络+数据结构与算法）

• Java架构进阶之开源框架篇（设计模式+Spring+SpringMVC+MyBatis）

• Java架构进阶之分布式架构篇 （限流（ZK/Nginx）+缓存（Redis/MongoDB/Memcached）+通讯（MQ/kafka））

• Java架构进阶之微服务架构篇（RPC+SpringBoot+SpringCloud+Dubbo+K8s）

本文已被CODING开源项目：【一线大厂Java面试题解析+核心总结学习笔记+最新讲解视频+实战项目源码】收录

需要这份系统化的资料的朋友，可以点击这里获取

• 第四部分：分布式（限流：ZK+Nginx；缓存：Redis+MongoDB+Memcached；通讯：MQ+kafka）

[外链图片转存中…(img-nyKrlOjW-1715456353465)]

• 第五部分：微服务（SpringBoot+SpringCloud+Dubbo）

[外链图片转存中…(img-0g6LhgCE-1715456353465)]

• 第六部分：其他：并发编程+设计模式+数据结构与算法+网络

[外链图片转存中…(img-3U6dGD2Y-1715456353466)]

进阶学习笔记pdf

• Java架构进阶之架构筑基篇（Java基础+并发编程+JVM+MySQL+Tomcat+网络+数据结构与算法）

[外链图片转存中…(img-iHWiCcvy-1715456353466)]

• Java架构进阶之开源框架篇（设计模式+Spring+SpringMVC+MyBatis）

[外链图片转存中…(img-Hu137v61-1715456353468)]

[外链图片转存中…(img-s9BxSdXJ-1715456353468)]

[外链图片转存中…(img-Y1I4EA04-1715456353469)]

• Java架构进阶之分布式架构篇 （限流（ZK/Nginx）+缓存（Redis/MongoDB/Memcached）+通讯（MQ/kafka））

[外链图片转存中…(img-JOuFPd4D-1715456353469)]

[外链图片转存中…(img-4W08chH5-1715456353469)]

[外链图片转存中…(img-uimTmQbM-1715456353469)]

• Java架构进阶之微服务架构篇（RPC+SpringBoot+SpringCloud+Dubbo+K8s）

[外链图片转存中…(img-djrfCVZR-1715456353470)]

[外链图片转存中…(img-HiLRIMzV-1715456353470)]

本文已被CODING开源项目：【一线大厂Java面试题解析+核心总结学习笔记+最新讲解视频+实战项目源码】收录

需要这份系统化的资料的朋友，可以点击这里获取