Hi Flyte community, Does using the pod template s...
# ask-the-community
j
Hi Flyte community, Does using the pod template setting for task registration completely override the pod template that Flyte defaults to or does it add to it? I'd like to add the following setting so my raw container Flyte task pods can refer to the their corresponding settings (based on stage/app):
Copy code
envFrom:
      - configMapRef:
          name: special-config
      - secretRef:
          name: special-config
https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/pod-configmap-envFrom.yaml
k
Cc @Dan Rammer (hamersaw) / @Byron Hsu
b
Yes it overrides the default podtemplate in the backend. The override is “append” if list/dict. “”Replace” if a single value
Do you run into any issue
d
To be more accurate - the default
PodTemplate
(in flytepropeller settings) is applied to the task by flytepropeller as the base configuration. If you specify a
pod_template_name
in the task decorate this will apply the specified k8s
PodTemplate
resource instead of the default
PodTemplate
(from propeller settings). However, if you use the
pod_template
argument in the task decorator to define an entire
PodTemplate
as an argument this will applied in addition to the default
PodTemplate
. We are working on getting this documented.
j
Thanks for clarifying!
110 Views