[Core Feature] PodSpec tasks without proto-defined custom #816
Labels
enhancement
New feature or request
flytekit
FlyteKit Python related issue
plugins
Plugins related labels (backend or frontend)
Milestone
Motivation: Why do you think this is important?
After #742 it would be good to move to another PodSpec definition for pod type tasks. We can use python k8s client to configure PodSpecs created using the OpenAPI spec, marshal that to a json dict and store that in the task custom.
However, we need to know the name of the primary container for plugin handler to monitor over the task execution lifecycle. To store this primary container name this change would require adding a "meta" type custom field.
Goal: What should the final outcome look like, ideally?
Pod tasks should be completely revamped and serve as a working template for tasks with non-proto defined custom fields.
Describe alternatives you've considered
The current pod spec implementation. This is no longer fully functional because quantity specification is now unsupported with the move to official k8s libraries.
[Optional] Propose: Link/Inline OR Additional context
If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document.
The text was updated successfully, but these errors were encountered: