Closed ese closed 1 year ago
@ese there seems to be inherent issue with this
Before applying check and heal wait for all expected pods up and running instead wait only for exists to let Kubernetes controllers do their job
Consider this scenario....
Those pods are unable to get scheduled.
In this case the check-and-heal would not do what its intended to do.
Consider another scenario...
In this case the check-and-heal would not configure the sentinels because of the fix here.
Description
In order to diagnose issues with the operator is more relevant to know what is happening with check and heal. We were logging mostly about kubernetes service performing updates in kubernetes objects which usually is not relevant once the cluster is bootstrapped.