acoustic-carpenter-78188
10/31/2023, 12:06 AMPod | Container
, but flytekit, allows using pod as a special task type. To achieve this the user has to install flytekitplugins-pod.
A preferred way would be to allow swapping out container vs pod for all containerized task executions. Let us consider the following example
@task(task_config=MyConfig(....))
def tk():
....
It should be possible to pass in the podconfig as follows
@task(task_config=MyConfig(...), pod=PodConfig())
def tk():
....
It is also ok to need flytekitplugins-pod to be installed to actually handle the right type
Goal: What should the final outcome look like, ideally?
The experience is detailed above. The reason to do this is so that in complicated cases, where users want to control the pod attributes, it should be trivial and possible
Describe alternatives you've considered
this is not easily possible. This has been implemented for ShellTasks as an example
Propose: Link/Inline OR Additional context
NA
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteacoustic-carpenter-78188
10/31/2023, 12:06 AMacoustic-carpenter-78188
11/02/2023, 8:36 PM