An alternative implementation that uses the Kubernetes API. Currently,
reactive-cli specifies this via arguments when it generates resources
for Kubernets targets. Thus, the default implementation for reactive-lib
remains one based on the service locator.
The main advantage of this is that we can discover pods that aren't yet ready,
perhaps they have health checks that rely on Akka Cluster being up.
An alternative implementation that uses the Kubernetes API. Currently, reactive-cli specifies this via arguments when it generates resources for Kubernets targets. Thus, the default implementation for reactive-lib remains one based on the service locator.
The main advantage of this is that we can discover pods that aren't yet ready, perhaps they have health checks that rely on Akka Cluster being up.