#3957 [Housekeeping] Remove datacatalog client from TaskExecutionContext Issue created by hamersaw Describe the issue In flyteorg/flytepropeller#485, caching was moved from the task-level to the node-level. Now, the catalog client included in the

TaskExecutionContext

is only used during maptask executions to perform bulk lookup for subtasks. The introduction of

ArrayNode

is mean to replace the maptask plugin and so when the k8s-array plugin is deprecated and remove we can remove the datacatalog client from the

TaskExecutionContext

. Additionally, we can remove the

PhaseWaitingForCache

from Task phases, as caching is no longer performed at the task level. What if we do not do this? Upon removing the maptask

k8s-array

plugin the catalog client is no longer needed in the

TaskExecutionContext

. Cleaning this up is just being a good steward. Related component(s) No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte