Provide a bare-bones "bastion Supervisor" container

[christophermaier]

We advise people to set up their Habitat networking with a "bastion ring" of 3 mutually-peered Supervisors running no services that other Supervisors (running services) can peer with, in order to provide robustness and resiliency in the face of network partitions.

Unfortunately, our Docker exporter is predicated around the notion of running a specific service, and not just the Supervisor by itself.

It'd be nice if we provided a Supervisor-only container just for this purpose.

[eeyun]

We do actually have supervisor only container one that gets built as part of the inbound changes for CI for core-plans and one thats been hand managed by fletcher. Neither of these are documented or published in a useful way for our users. Once the CI bits are in place I think we can likely just document where it is and how to use it, which should complete this card!

[baumanj]

Confirmed valid with v0.57, keeping

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[christophermaier]

There's no reason not to do this.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.