When Argo Workflows runs your workload, your container isn't alone in its pod. Argo wraps other containers and volumes around it to feed your code its inputs and carry the results back out, and most people never notice any of that is happening.

This talk opens up the pod. We'll look at what each piece does: how your parameters and artifacts get in before your code starts, how the outputs and logs get back out after it finishes, and the little shared filesystem Argo uses to pass it all between containers. You'll come away actually knowing what Argo does for you every time a step runs.

Then we'll get to what's changed. Every Argo pod used to begin with an init container that staged things before your work started. Kubernetes now supports image volumes, which means we can drop that init container entirely. I'll show how this new opt-in feature in Argo Workflows 4.1 works, what you get for it, and the small things worth knowing before you switch it on.