Command order at runtime with secret distribution #2030 and dynamic configuration #2068

[stp-ip]

This is a really early draft of how the different bootstrapping tools could be ordered and how they interact. It uses concepts from #2030 and #2068 heavily. Until these are pinpointed it's quite drafty.

Build container based on ENVs and config templates
Build encrypted Data Volume Container with GPG encryption and moby/moby#8021
Deploy via k8s and ENV-file
Bind Data Volume Container to /var/secrets
Use ENVs (with seed secret) to decrypt Data Volume Container -> seed secret = gpg key?
Use endpoint "/bootstrap.sh"
-> Run /var/secrets/ENVs.sh for credentials, PWs etc. if backend=env
-> Run /keys.sh to copy keys to actual locations
-> Run confd with ENV/etcd/consul to produce config files
-> Start actual process via confd

Needs a lot more input!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close