with

@kubernetes

the step gets its own pod, yet i notice that for each subsequent run a new pod is spawned. is it possible to stop/delete the pod automatically after the flow is done?

When running a flow that has

@kubernetes

or having

--with kubernetes

on the cli results in the following: • Every

@step

runs as a Kubernetes job (which spawns a pod) • The Kubernetes job has a TTL of 7 days. So, the pods will get deleted after 7 days automatically. • As a user, you don't have to delete the pods yourself.

+1 to @User. It’s worth noting that as soon as the task finishes, the pod resources are released back to the cluster.