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

Flyte

After a recent update to our flyte helm chart, recovery has stopped working. We can relaunch still but we are getting an error
```Failed to check the existence of deck file.```

We get that error in the propellor when we hit recover

<@U03BSHYHQ1K> sorry about this bug. It has been fixed in <https://github.com/flyteorg/flytepropeller/pull/506|this PR>. The bug was introduced <https://github.com/flyteorg/flytepropeller/pull/495|here>. So updating the FlytePropeller version will fix this.

<https://github.com/flyteorg/flyteplugins/blob/902b902fcf487f30ebb5dbeee3bb14e17eb0ec21/go/tasks/pluginmachinery/flytek8s/config/config.go#L133> <@U04DSFUUQQN> this is the config option in case you haven’t found it already

let’s bump that to 8 mins.  should be enough.

```// This may consist of:
								// 1. Transient errors: e.g. failed to reserve
								// container name, container name [...] already in use
								// by container
								// 2. Permanent errors: e.g. no command specified
								// To handle both types of errors gracefully without
								// arbitrary pattern matching in the message, we simply
								// allow a grace period for kubelet to resolve
								// transient issues with the container runtime.```


to “handle both types of errors gracefully…”