https://flyte.org logo
#flyte-deployment
Title
# flyte-deployment
c

Cody Scandore

08/14/2023, 1:21 PM
Could I add tolerations on the
flyte-binary
helm chart values.yaml to schedule the pod onto a node with taints?
d

David Espejo (he/him)

08/14/2023, 3:37 PM
Hi @Cody Scandore I think in this case you can make use of
Pod Templates
and then you can either: 1. Make that Pod Template a default by adding the following to the flyte binary configmap:
Copy code
copilot:
    plugins:
      k8s:
        # -- Structure documented [here](<https://pkg.go.dev/github.com/lyft/flyteplugins@v0.5.28/go/tasks/pluginmachinery/flytek8s/config#FlyteCoPilotConfig>)
        co-pilot:
          name: flyte-copilot-
          image: <http://cr.flyte.org/flyteorg/flytecopilot:v0.0.32|cr.flyte.org/flyteorg/flytecopilot:v0.0.32> # FLYTECOPILOT_IMAGE
          start-timeout: 30s
         
        default-pod-template-name: <your_template_name>
See docs 2. Invoke the Pod Template from the task itself (see also docs) In both cases, though, you have to created the Pod Template resource first
c

Cody Scandore

08/14/2023, 3:40 PM
Thanks David! What about tolerations on the flyte-binary pod itself?
d

David Espejo (he/him)

08/14/2023, 3:59 PM
uh sorry, a different thing. I don't see the
flyte-binary
templates accepting changes to the backend Pod spec from values. I think you could try editing the Pod itself.
tolerations
is one of the fields that can be changed through
kubectl edit
c

Cody Scandore

08/14/2023, 4:31 PM
This seemed to work for me in the values.yaml
Copy code
configuration:
  ...
deployment:
  extraPodSpec:
    tolerations:
      - key: "dedicated"
        operator: "Equal"
        value: "flyte"
        effect: "NoSchedule"
There is a corresponding taint on the nodegroup.
d

David Espejo (he/him)

08/14/2023, 4:35 PM
right! I just noticed the
{{- if .Values.deployment.extraPodSpec }}
in the
configmap
template
13 Views