Kubernetes在目录中并行化多个样本

"如果您希望作业的每个实例都在不同的节点上，您可以使用daemonSet，这正是它所做的，为每个工作节点提供1个pod。

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

https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/

另一种方法 - 使用pod antiaffinity：

affinity:

podAntiAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    - labelSelector:
        matchExpressions:
          - key: ""app""
            operator: In
            values:
            - zk
      topologyKey: ""kubernetes.io/hostname""

requiredDuringSchedulingIgnoredDuringExecution字段告诉Kubernetes Scheduler它永远不应该在topologyKey定义的域中共同定位两个具有app标签为zk的Pod。topologyKey kubernetes.io/hostname表示域是单个节点。使用不同的规则，标签和选择器，您可以扩展此技术，以跨物理，网络和电源故障域传播整体"