Matt Rasmussen

@dakoner I self commented the changes I've made thus far. Feel free to incorporate these into #19.

Thanks @heuermh for the ideas and links. It's very helpful. Hopefully, many of these tools can be used within a redun task as-is. One design goal of redun was to...

Thanks for a great question. > My question is the following: would it be a good idea to hash all the internal source code invoked by a task? Would it...

Thanks @spitz-dan-l for posting this. The current behavior is opinionated. As you state, if the scheduler is killed (e.g. with Ctrl+C) the AWS Batch jobs do continue until completion. If...

Thanks for sharing this @TylerSpears. We originally picked pickle version 3 for backwards compatibility, but as you point out it has this limitation on data size. As you correctly point...

> It would be nice to have the flexibility to stage by copying in or stage by mount - but I imagine you could configure two different 'executors' (actually running...

> @dakoner @mattrasmus this [line](https://github.com/insitro/redun/blob/k8s-rasmus/redun/executors/k8s_utils.py#L180) needs to be changed to: > > ```python > container = client.V1Container(name=name, image=image, args=command, env=env) > ``` Thanks @ricomnl for pointing this out! We'll incorporate.

Thanks everyone! I'll merge this first beta version of k8s support as is now, and we can continue to refine/improve in smaller follow up PRs.