#1564 When running in a k8s cluster with mutating webhooks, tasks don't finish since the side car is still working [Core Feature] Issue created by NotMatthewGriffin Motivation: Why do you think this is important? Currently when running a flyte task in a kubernetes cluster that uses mutating webhooks to add sidecars to all pods, the task and associated pod will run until terminated in the flyte web console. Inside of the pod, the container actually running the flyte task has completed and exited with a good status but the sidecar container is still running. To work around this a user must specify the task in their workflow as a pod task like

@task(task_config=Pod(pod_spec=pod_spec, pimary_container_name="container_name"))

. This means that users need to know the configuration of the cluster ( like will any sidecars be added automatically) in order to successfully create/run a flyte workflow. Goal: What should the final outcome look like, ideally? Ideally a user of flyte wouldn't need to declare their task as a pod task in order to run it in a kubernetes cluster that uses mutating webhooks to add sidecars to pods. The user could declare their task like

@task

and it would run the flyte task pod until the flyte task container finishes then the rest of the workflow would be run. Describe alternatives you've considered The only other alternative I've considered is continuing to use the workaround of declaring all workflows/tasks as pod tasks. flyteorg/flyte

#1564 When running in a k8s cluster with mutating webhooks, tasks don't finish since the side car is still working [Core Feature] Issue closed as not planned by github-actions[bot] flyteorg/flyte