一个DaemonSet对象能确保其建立的Pod在集群中的每一台(或指定)Node上都运行一个副本。node
若是集群中动态加入了新的Node,DaemonSet中的Pod也会被添加在新加入Node上运行。删除一个DaemonSet也会级联删除全部其建立的Pod。下面是一些典型的DaemonSet的使用场景:git
下面的描述文件建立了一个运行着fluentd-elasticsearch镜像的DaemonSet对象:github
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: fluentd-elasticsearch
namespace: kube-system
labels:
k8s-app: fluentd-logging
spec:
selector:
matchLabels:
name: fluentd-elasticsearch
template:
metadata:
labels:
name: fluentd-elasticsearch
spec:
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
containers:
- name: fluentd-elasticsearch
image: k8s.gcr.io/fluentd-elasticsearch:1.20
resources:
limits:
memory: 200Mi
requests:
cpu: 100m
memory: 200Mi
volumeMounts:
- name: varlog
mountPath: /var/log
- name: varlibdockercontainers
mountPath: /var/lib/docker/containers
readOnly: true
terminationGracePeriodSeconds: 30
volumes:
- name: varlog
hostPath:
path: /var/log
- name: varlibdockercontainers
hostPath:
path: /var/lib/docker/containers
在Kubernetes 1.8以后,必须指定.spec.selector
来肯定这个DaemonSet对象管理的Pod,一般与.spec.template.metadata.labels
中定义的Pod的label一致。docker
.spec.template.spec.nodeSelector
或
.spec.template.spec.affinity
,DaemonSet Controller会将Pod建立在特定的Node上。
unschedulable
属性会被DaemonSet Controller忽略。