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

Flyte

Hi! Is there a way to shorten `ttlSecondsAfterFinished`? By default, it is 3600s (1 hour) and we’d like to tear down a cluster right after a job is complete. Thanks for your help!
```$ k describe rayjobs feb5da8c2a2394fb4ac8-n0-0 -n flytesnacks-development
...
  Ttl Seconds After Finished:   3600```

yes. update the propeller config map. change ttl to 0

<https://docs.flyte.org/en/latest/deployment/cluster_config/flytepropeller_config.html#ray-ray-config>

Thanks for your prompt reply! Let me try this!

It worked like a charm!
```$ kubectl describe rayjobs f3281d8b2689c4c35a67-n0-0  -n flytesnacks-development
  Ttl Seconds After Finished:   60```
For those who want to do the same, add this `ray.ttlSecondsAfterFinished` to the values.yaml for flyte-core.
```  # -- Kubernetes specific Flyte configuration
  k8s:
    plugins:
      ray:
        ttlSecondsAfterFinished: 60```