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

Flyte

We have just submitted a RFC for the eviction of cached task outputs (and proposing the addition of a basic `flyteadmin` API for clearing the cache of completed executions): <https://github.com/flyteorg/flyte/pull/2633>

Thank you for the initial feedback to <@U029U35LRDJ>. As this change could have a slightly larger impact on Flyte, we'd be happy about some extra thoughts or ideas some of you might have - any comments would be appreciated!

<@U029U35LRDJ> (sorry to ping you directly again :sweat_smile: ) any input on the additional suggestion left by <@U0327P2QCAU> on github: <https://github.com/flyteorg/flyte/pull/2633#issuecomment-1170875716>? is that something we should look into including in this RFC, or keep separate?

it's definitely something could see being useful for our use cases, just not sure if we should split it (so we don't bloat the scope too much) or not

Left a <https://github.com/flyteorg/flyte/pull/2633#issuecomment-1175591775|comment on github>. TL;DR I think it could be a very useful feature and the cache eviction API makes it possible. However, I think there are enough unknowns and required discussion that it makes sense to track it separately.