Mccalluc/first steps

[mccalluc]

This has a lot of plumbing, and one passing test.

For django-docker, we'll need a compatibility layer of some sort for anything we do that goes beyond Docker, whether that's ECS, EKS, Fargate, or wrapping our own Kubernetes interface... but, it doesn't necessarily need to be at the API level like this. If it were the case that the high-level functions we are interested in are accomplished differently on these different frameworks, then we'd want compatibility at that higher level... but I don't think that's the case here: We need the same basic functionality everywhere, and that corresponds to what the API offers.

I think targeting raw Kubernetes first makes sense:

• Local development is possible (with minikube)
• AWS technologies are built on top of it, so it's not going to hurt to understand what's underneath.
• I'm still not convinced that what AWS offers makes our job easier... I think it makes other jobs easier, and I'm not sure we've chosen the right job here... but for what we're trying to do, I think this is a good way to do it.