Service to access directly master and slaves instances in Redis was added in #627, This exposes the service publicly using loadBalancers.
To make it security by default the service is changed to only expose internally in the cluster. Let the user to create their ow service if exposing publicly is the option until its available in the operator by a config set.
Running pods can surge the number of expected replicas during rollouts of a deployment change in sentinels, while a new version of the template is deployed. In anycase we will always consider not running while there are pods terminating or pending .
Service to access directly master and slaves instances in Redis was added in #627, This exposes the service publicly using loadBalancers. To make it security by default the service is changed to only expose internally in the cluster. Let the user to create their ow service if exposing publicly is the option until its available in the operator by a config set.
Running pods can surge the number of expected replicas during rollouts of a deployment change in sentinels, while a new version of the template is deployed. In anycase we will always consider not running while there are pods terminating or pending .