k8s docker-compose

[jacobweinstock]

Description

This PR brings up the sandbox via Docker compose using the Kubernetes backend for all service. This does not completely remove the postgres backend setup but moves all the compose with postgres into an isolated directory (deploy/compose/postgres) that can be removed when we're ready.

I did not touch the terraform setup. I need some help validating that one. please and thank you. CC @mmlb @displague

Why is this needed

Fixes: #142 #45 #118 #131 #133 #145 #148

• This "fixes" a quite a few issues related to TLS cert generation. This is the case because we are not using TLS in this deployment. Also see, https://github.com/tinkerbell/tink/issues/555.
• This also "fixes" any issues related to the internal registry as that is removed as the default.

How Has This Been Tested?

Manually tested vagrant with virtualbox (on a Mac), vagrant with libvirt (on Ubuntu 22.04), and docker-compose (on on Ubuntu 22.04).

How are existing users impacted? What migration steps/scripts do we need?

There is no migration support. Users will need to follow a quick start guide to get started.

Checklist:

I have:

• [x] updated the documentation and/or roadmap (if required)
• [ ] added unit or e2e tests
• [ ] provided instructions on how to upgrade

[mmlb]

looks pretty good to me, if all looks good after I run it we can merge