Ephemeral storage is respected from the overlod for peon tasks

[churromorales]

I noticed during testing that the ephemeral storage resource was not inherited from the overlord. We should only be overriding the specific "cpu" and "memory" resources, currently we are calculating cpu/memory and only setting those. We should inherit all the other resources and only override cpu and memory

[gianm]

I am not a k8s expert so this is perhaps a basic question, but: is the effect of this that task pods will end up with the same ephemeral storage requirement as the Overlord pod that launched them? If so I don't understand why this is necessarily good -- wouldn't tasks generally need different amount of storage than the Overlord?

[churromorales]

@gianm this is a good point, i want to inherit properly from the overlord, then have another PR to override. But first I should be doing the right thing, unless you think both can go in this PR. If you don't inherit, you use the default value, which is immutable....you can't change it.

[gianm]

Got it, that makes sense. It's ok to do the next step as a follow-up IMO, so I'll merge this one.