echoing-carpenter-92090
08/14/2023, 1:21 PMflyte-binary
helm chart values.yaml to schedule the pod onto a node with taints?average-finland-92144
08/14/2023, 3:37 PMPod Templates
and then you can either:
1. Make that Pod Template a default by adding the following to the flyte binary configmap:
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 firstechoing-carpenter-92090
08/14/2023, 3:40 PMaverage-finland-92144
08/14/2023, 3:59 PMflyte-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
echoing-carpenter-92090
08/14/2023, 4:31 PMconfiguration:
...
deployment:
extraPodSpec:
tolerations:
- key: "dedicated"
operator: "Equal"
value: "flyte"
effect: "NoSchedule"
There is a corresponding taint on the nodegroup.average-finland-92144
08/14/2023, 4:35 PM{{- if .Values.deployment.extraPodSpec }}
in the configmap
template