gorgeous-beach-23305
11/30/2023, 3:27 PMdefault-node-selector:
in the k8s plugin config to select nodes on our MNG for flyte workers pods. This allows us to use either spot nodes of on-demand nodes on AWS. We want to set up nodeAffinity selectors with weights to try to use spot first and if not available, go to on-demand nodes. We are using flyte-binary chart and the deployment
section in values.yaml has a extraPodSpec
which I believe only applies to the flyte-binary pods. Are pod templates the only way to apply nodeAffinity selection rules to worker pods? Or is there any way to apply these via the values.yaml for flyte-binary?tall-lock-23197
gorgeous-beach-23305
12/06/2023, 11:00 AMnodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 100
preference:
matchExpressions:
- key: node.myorg/lifecycle
operator: In
values:
- flyte-spot
- weight: 50
preference:
matchExpressions:
- key: node.myorg/lifecycle
operator: In
values:
- flyte
flyte-spot
is the spot MNG and flyte
is the on demand MNG.
I saw there is a default-affinity section in the k8s plugin config, but I am not able find any example of this and am not sure I can set the above settings there. Can you help me find where I can set this nodeAffinity setting?tall-lock-23197
average-finland-92144
12/06/2023, 5:28 PMflyte-binary
or flyte-core
?average-finland-92144
12/06/2023, 9:28 PMaffinity
config and then set it as the default as indicated here. I haven't tried it my self yet but already tried the default-affinity
section with no successgorgeous-beach-23305
12/07/2023, 9:22 AMflyte-binary