Summary
The user seeks recommendations for modifying a workflow during the registration phase using a mutating webhook to add a task without user management, emphasizing the need for these changes to occur before registration due to compiler checks. They mention Flytekit's new on_failure argument and question the necessity of a finally option. Their use case involves managing Kubernetes resources through a custom task that should integrate with other tasks in a workflow, ensuring resources are terminated after training tasks, as Flyte currently lacks a mechanism for this. The user is considering creating another sensor agent for orchestrated garbage collection and highlights their choice of the Flyte agent route to leverage the framework without changes across the stack for easier testing and production operation. They note that Kevin has assisted with some initial agent use cases and problems, and express concern about the hackiness of invoking cleanup from a get method, questioning if they can refer to Kubernetes resources created by a custom agent task in another workflow.