Consul sidecar container

Relates to #3

Ideally looking for a language agnostic way to implement consul service discovery inside the deployment of helmcharts.

Right now for example this package uses a node_module I developed to simply make curl calls to consul to register/de-register the service when the service goes up or down, with some service information and a TTL check.

Will be toying with some ideas on the easiest way to pass relevant information to the consul servers.

Slightly relevant (more a reminder), afterwords it'd be nice to get consul as a helm release/cluster service instead of directly on nodes in os/workbench> that would eventually be tied to k8s ingress.