From d55e1ff251b3494605dd6c01da5c3a27a1291315 Mon Sep 17 00:00:00 2001 From: Siddhant Rai <47355538+siiddhantt@users.noreply.github.com> Date: Fri, 4 Oct 2024 23:42:13 +0530 Subject: [PATCH] update: remove note as requested change Signed-off-by: Siddhant Rai <47355538+siiddhantt@users.noreply.github.com> Signed-off-by: Siddhant Rai --- docs/flyte_fundamentals/registering_workflows.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docs/flyte_fundamentals/registering_workflows.md b/docs/flyte_fundamentals/registering_workflows.md index c40ad279cc..8854a26560 100644 --- a/docs/flyte_fundamentals/registering_workflows.md +++ b/docs/flyte_fundamentals/registering_workflows.md @@ -352,15 +352,6 @@ a {py:class}`~flytekit.remote.remote.FlyteRemote` object. You can learn more about how to do this {ref}`here `. ``` -```{note} -When using `pyflyte` to run jobs, the `k8sPod.dataConfig` section is automatically added to the task configuration. This section is crucial to ensure the task has access to the necessary input files. - -In earlier versions, some users experienced an issue where the `k8sPod.dataConfig` section was missing when registering workflows via `flytectl register files`. This omission resulted in tasks failing due to unavailable input files. - -**Resolution:** -This issue has been addressed in a recent update, where the hydration of the `taskspec` now correctly includes the `dataConfig` for Kubernetes pods. So ensure you are using the latest versions of Flyte components where this fix has been implemented. -``` - ## CI/CD with Flyte and GitHub Actions You can use any of the commands we learned in this guide to register, execute,