Summary
The user is deploying a Flyte binary on a Kubernetes environment and is facing an issue where a task that requires access to credentials is not receiving the volumeMounts in the task execution pod, despite having created a PodTemplate with volumeMounts for secret files. They are looking for a solution to manage the Secrets used in each task and are inquiring if others have experienced a similar issue.
jeremy221
Just found the answer, we can simply define all of those things in PodTemplate and use it. Found a way to custom PodTemplate for task execution task too
jeremy221
Hello Flyte community, I deploy Flyte binary on Kubernetes environment and currently, I have a task that needs to access some credentials, so I create a PodTemplate with volumeMount to mount secret files to a certain path. But it seems the task execution pod only gets the volumes section without volumeMounts. I know it can be solved in the task code but I want to take control over the Secret that are used in each task in Kubernetes. Has anyone encountered a similar situation or found a solution for this case? Thank you!