电子商务网站建设课,公司设计网页设计,响应式网站项目,昆明做网站推1.1DaemonSet是什么
Deployment部署的副本Pod会分布在各个Node上#xff0c;每个Node都可能运行好几个副本。DaemonSet的不同之处在于#xff1a;每个Node上最多只能运行⼀个副本。DaemonSet的典型应用场景有#xff1a; #xff08;1#xff09;在集群的每个节点上运⾏存…1.1DaemonSet是什么
Deployment部署的副本Pod会分布在各个Node上每个Node都可能运行好几个副本。DaemonSet的不同之处在于每个Node上最多只能运行⼀个副本。DaemonSet的典型应用场景有 1在集群的每个节点上运⾏存储Daemon比如glusterd或ceph。 2在每个节点上运行日志收集Daemon比如flunentd或logstash。 3在每个节点上运行监控Daemon比如PrometheusNodeExporter或collectd。
其实Kubernetes自己就在用DaemonSet运行系统组件。执行如下命令如下所示。
kubectl get daemonset --namespacekube-system
kubectl get daemonset --namespacekube-flannel
[rootk8s-master ~]# kubectl get daemonset --namespacekube-flannel
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
kube-flannel-ds 3 3 3 3 3 none 10d
[rootk8s-master ~]# kubectl get daemonset --namespacekube-flannel
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
kube-flannel-ds 3 3 3 3 3 none 10dDaemonSet kube-flannel-ds和kube-proxy分别负责在每个节点上运⾏flannel和kube-proxy组件在通过查看Pod副本看看各个节点的分布情况
kubectl get pod --namespacekube-system -o wide[rootk8s-master ~]# kubectl get pod --namespacekube-system -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
coredns-7ff77c879f-ltqn4 1/1 Running 2 10d 10.244.0.8 k8s-master none none
coredns-7ff77c879f-xb6qm 1/1 Running 2 10d 10.244.0.9 k8s-master none none
etcd-k8s-master 1/1 Running 2 10d 192.168.200.128 k8s-master none none
kube-apiserver-k8s-master 1/1 Running 2 10d 192.168.200.128 k8s-master none none
kube-controller-manager-k8s-master 1/1 Running 2 10d 192.168.200.128 k8s-master none none
kube-proxy-dcprp 1/1 Running 2 10d 192.168.200.128 k8s-master none none
kube-proxy-nklr5 1/1 Running 2 10d 192.168.200.129 k8s-node1 none none
kube-proxy-slslc 1/1 Running 4 10d 192.168.200.130 k8s-node2 none none
kube-scheduler-k8s-master 1/1 Running 2 10d 192.168.200.128 k8s-master none none
metrics-server-7f6b85b597-k6b26 1/1 Running 2 10d 10.244.1.29 k8s-node1 none none
1.2 DaemonSet的创建和运行
本小节以Prometheus Node Exporter为例演示用户如何运行自己的DaemonSet。Prometheus 是 流行的系统监控方案 Node Exporter 是Prometheus的agent以Daemon的形式运行在每个被监控节点 上。 vi node-exporter.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:name: node-exporter-daemonsetnamespace: agent
spec:selector:matchLabels:app: prometheustemplate:metadata:labels:app: prometheusspec:hostNetwork: truecontainers:- name: node-exporterimage: prom/node-exporterimagePullPolicy: IfNotPresentcommand:- /bin/node_exporter- --path.procfs- /host/proc- --path.sysfs- /host/sys- --collector.filesystem.ignored-mount-points- ^/(sys|proc|dev|host|etc)($|/)volumeMounts:- name: procmountPath: /host/proc- name: sysmountPath: /host/sys- name: rootmountPath: /rootfsvolumes:- name: prochostPath:path: /proc- name: syshostPath:path: /sys- name: roothostPath:path: /先创建个命名空间
kubectl create namespace agent通过kubectl创建资源
kubectl apply -f node-exporter.yaml然后通过kubectl查看Pod分布情况
[rootk8s-master ~]# kubectl get pod --namespaceagent -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
node-exporter-daemonset-5rrq4 1/1 Running 1 44h 192.168.200.129 k8s-node1 none none
node-exporter-daemonset-hjkzs 1/1 Running 1 44h 192.168.200.130 k8s-node2 none none
2.1 Job
容器按照持续运行的时间可分为两类服务类容器和工作类容器。 服务类容器通常持续提供服务需要⼀直运行比如HTTPServer、Daemon等。工作类容器则是⼀次性任务比如批处理程序完成后容器就退出。 Kubernetes的Deployment、ReplicaSet和DaemonSet都用于管理服务类容器 对于工作类容器我们使用Job。先看⼀个简单的Job配置文件件myjob.yml。
vi myjob.yml
apiVersion: batch/v1
kind: Job
metadata:name: myjobnamespace: jobs
spec:template:metadata:labels:app: myjobspec:containers:- name: hello-jobimage: busyboximagePullPolicy: IfNotPresentcommand: [echo, hello k8s job!]restartPolicy: Neverkubectl apply -f myjob.yml通过查看Job运行情况可以知道其运行结束就结束了如下图所示变成了Completed状态。
kubectl get pod -n jobs[rootk8s-master ~]# kubectl get pod -n jobs
NAME READY STATUS RESTARTS AGE
myjob-krgdh 0/1 Completed 0 44h还可以通过查看Log看看这个Job留下的足迹
kubectl logs myjob-krgdh -n jobs #查看日志
kubectl describe pods/myjob-krgdh --namespace jobs #查看job描述ng)
[rootk8s-master ~]# kubectl logs myjob-krgdh -n jobs
hello k8s job!
[rootk8s-master ~]# kubectl describe pods/myjob-krgdh --namespace jobs
Name: myjob-krgdh
Namespace: jobs
Priority: 0
Node: k8s-node2/192.168.200.130
Start Time: Sat, 27 Jan 2024 16:53:58 0800
Labels: appmyjobcontroller-uid1a312a0b-b6eb-4219-958f-801edc224608job-namemyjob
Annotations: none
Status: Succeeded
IP: 10.244.2.14
IPs:IP: 10.244.2.14
Controlled By: Job/myjob
Containers:hello-job:Container ID: docker://0403ccea759585e45f39431bf3958a169211210ef948a0b7c1d4be1ed411e272Image: busyboxImage ID: docker-pullable://busyboxsha256:5acba83a746c7608ed544dc1533b87c737a0b0fb730301639a0179f9344b1678Port: noneHost Port: noneCommand:echohello k8s job!State: TerminatedReason: CompletedExit Code: 0Started: Sat, 27 Jan 2024 16:53:59 0800Finished: Sat, 27 Jan 2024 16:53:59 0800Ready: FalseRestart Count: 0Environment: noneMounts:/var/run/secrets/kubernetes.io/serviceaccount from default-token-vz4wm (ro)
Conditions:Type StatusInitialized TrueReady FalseContainersReady FalsePodScheduled True
Volumes:default-token-vz4wm:Type: Secret (a volume populated by a Secret)SecretName: default-token-vz4wmOptional: false
QoS Class: BestEffort
Node-Selectors: none
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300snode.kubernetes.io/unreachable:NoExecute for 300s
Events: none
2.2 并行Job
如果希望能够同时并行运行多个Pod以提高Job的执行效率Job提供了一个贴心的配置parallesim。例如下面的配置我们将上面的小Job改为并行运行的Pod数量设置为3。 修改 myjob.yml
apiVersion: batch/v1
kind: Job
metadata:name: testjob
spec:parallelism: 3template:metadata:labels:app: testjobspec:containers:- name: hello-jobimage: busyboximagePullPolicy: IfNotPresentcommand: [echo, hello k8s job!]restartPolicy: Neverkubectl get pod -o wide -n default可以看出Job一共启动了3个Pod都是同时结束的可以看到三个Pod的AGE都是相同的。
[rootk8s-master ~]# kubectl get pod -o wide -n default
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
testjob-jmlzm 0/1 Completed 0 44h 10.244.2.18 k8s-node2 none none
testjob-r62f4 0/1 Completed 0 44h 10.244.2.17 k8s-node2 none none
testjob-vg7c6 0/1 Completed 0 44h 10.244.2.16 k8s-node2 none none
2.3 定时Job
Linux中有cron程序定时执行任务Kubernetes的CronJob提供了类似的功能可以定时执行Job。 vi hello-cron-job.yml
apiVersion: batch/v1beta1
kind: CronJob
metadata:name: hello-cron-jobnamespace: jobs
spec:schedule: */1 * * * *jobTemplate:spec:template:spec:containers:- name: hello-cron-jobimage: busyboximagePullPolicy: IfNotPresentcommand: [echo, hello edisons k8s cron job!]restartPolicy: OnFailure上面加粗的配置是CronJob的独有配置需要注意的是schedule它的格式和Linux Cron一样这里的*/1 * * * *代表每一分钟启动执行一次。对于CronJob它需要的是jobTemplate来定义Job的模板。
kubectl get cronjob -n jobs[rootk8s-master ~]# kubectl get cronjob -n jobs
NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE
hello-cron-job */1 * * * * False 0 43h 43h查看job
可以看到在过去的三分钟里每一分钟都启动了一个Pod符合预期。
kubectl get jobs -n jobs[rootk8s-master ~]# kubectl get jobs -n jobs
NAME COMPLETIONS DURATION AGE
hello-cron-job-1706350440 1/1 1s 43h
hello-cron-job-1706350500 1/1 1s 43h
hello-cron-job-1706350560 1/1 1s 43h
