What’s going on with the ContainerD support, and more specifically, why are y’all adding ContainerD support? I can see a lot of things on GitHub talking about making progress with it, but I’m a bit unclear as to the motivations.
I’d always naively assumed (I am a simpleton) that there would be more benefit using Kubes as a backend directly, and that using another container runtime directly won’t really help with things like auto-scaling, or convincing all the Cloud Native cool kids that Concourse isn’t a CI system for boomers.
Is the ContainerD support a vital step towards working more natively with Kubes? Or is it a stepping stone, driving out abstractions by supporting something simpler than Kubes whilst still not being Garden?