3 ms·
> deploy to AWS vs an internally-hosted kube This is IMHO one of the absurdities of current could technology. We have the technology and know-how to not make
by dathinab 3y ago
> deploy to AWS vs an internally-hosted kube
This is IMHO one of the absurdities of current could technology.
We have the technology and know-how to not make this different skills, to make it mostly uniform and abstract away all the compute hosting specific parts in the same way that compilers mostly abstract away most ISA/hardware details (at least for most languages and many use-cases, not all)
- technofiend 3y agoI was disappointed (not that I'm picking on them) to learn Hashicorp's terraform didn't do exactly the sort of abstraction you're talking about. You can cobble together layers of automation, but I share your disappointment that there's not a single solution. Although I will say rackn's digital rebar gets a lot of the way there. You can deploy workloads in a pretty technology-agnostic fashion for the things it does support, and it can be integrated/extended with ansible, terraform and other scripting tools (including plain old bash) or other languages as needed.