This isn't necessarily a fix, but the additional logging may help us in
determining what the underlying issue is and it seems sensible to
confirm that the current and updated revision numbers also match as part
of the readiness check.
Contributes-to: #10163
Signed-off-by: Dominic Evans <dominic.evans@uk.ibm.com>
c.log("StatefulSet is not ready: %s/%s. currentRevision %s does not yet match updateRevision %s",sts.Namespace,sts.Name,sts.Status.CurrentRevision,sts.Status.UpdateRevision)
returnfalse
}
c.log("StatefulSet is ready: %s/%s. %d out of %d expected pods are ready",sts.Namespace,sts.Name,sts.Status.ReadyReplicas,replicas)