As of now as it resolves a bunch of problems with kubectl rollout status:
- rollout status before could hit a race condition:
  it would look for deployment status, before ReplicaSet is created, thus leading to premature return, before the credentials could be used,
- the new rollout status does correctly and adhere to deployment strategies as it should