使用kubeadm部署高可用Kubernetes 1.17.0 设置了三个Master节点,而后在部署Heketi过程当中发现,Daemonset不启动相应的pod。原来须要设置Kubernetes的Master节点参与应用调度(默认安装Master节点不运行应用)。有两种方法:node
长期改变节点的属性,容许Master运行应用,执行:docker
kubectl taint nodes --all node-role.kubernetes.io/master-
临时容许Master节点执行应用,在应用的yaml文件中添加:api
tolerations: - key: node-role.kubernetes.io/master effect: NoSchedule
我这里测试使用:app
apiVersion: apps/v1 kind: DaemonSet metadata: name: fluentd-elasticsearch namespace: test 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: quay.io/fluentd_elasticsearch/fluentd:v2.5.2 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
而后保存为test.yaml,运行:kubectl apply -f test.yaml,pod被创建起来。elasticsearch
若是没有tolerations的设置,虽然运行成功,但pod仅在worker节点运行,若是只有master节点,则不会启动pod。测试