201-configmap.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  name: scheduler-config
  namespace: kube-system
data:
  scheduler-config.yaml: |
    apiVersion: kubescheduler.config.k8s.io/v1
    kind: KubeSchedulerConfiguration
    # clientConnection.kubeconfig not necessary since the scheduler-plugin
    # deployment can pick up the cluster's kubeconfig
    # (See https://github.com/kubernetes-sigs/scheduler-plugins/issues/188#issuecomment-822475393)
    leaderElection:
      # TODO: Figure out if we need leader election enabled.
      # https://kubernetes.io/docs/tasks/extend-kubernetes/configure-multiple-schedulers/#enable-leader-election
      leaderElect: false
    profiles:
    # If set to "default-scheduler", this scheduler profile will be used for all pods by default
    # Otherwise, you must set the scheduler name in the pod template
    # (See https://kubernetes.io/docs/tasks/extend-kubernetes/configure-multiple-schedulers/#define-a-kubernetes-deployment-for-the-scheduler)
    - schedulerName: "one-node-per-pipelineRun"
      plugins:
        # See https://kubernetes.io/docs/reference/scheduling/config/#scheduling-plugins for a list of all other plugins
        # that are enabled by default
        multiPoint:
          enabled:
          - name: OneNodePerPipelineRun
      pluginConfig:
      - name: OneNodePerPipelineRun
        args:
          isolationStrategy: "colocateCompleted" # Options are "colocateAlways", "colocateCompleted" and "isolateAlways"