https://flyte.org
Join Slack
I created a Kubernetes PodTemplate in the same namespace as my flyte-propeller pod, and the template...
# flyte-support
s
I created a Kubernetes PodTemplate in the same namespace as my flyte-propeller pod, and the template gets used successfully when creating new pods. However, the new pods fail to include the init container upon launching which I specify in the template. I named the container 
default
and the init container 
default-init
just like the instructions in section "Create a PodTemplate resource" from this documentation page says, but I still don't see the init container being lauched along with my example pod. Anyone know why this could be happening?
c
I am guessing you're encountering this: https://github.com/flyteorg/flyte/issues/6204
I don't believe pod templates supporting injecting arbitrary containers, just modifying existing ones
Per the docs
Copy code
In this scheme, if the default PodTemplate contains a container with the name "default", that container will be used as the base configuration for all containers Flyte constructs. Similarly, a container named "primary" will be used as the base container configuration for all primary containers.
key part being "all containers Flyte constructs"
I see a value in the use case for injecting certain types of init containers but this would be a new feature requests and would have to be thought about carefully so its not injecting incomplete, broken containers for folks in situations where there aren't existing init-containers if that makes sense.
s
I see
20 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by