fix bug: sts status conflict between kubesphere and kubernetes

Created by: styshoo

fix bug: sts status conflict between kubesphere and kubernetes

What type of PR is this?

/kind bug

What this PR does / why we need it:

If no pods of sts starts, the kubectl will show a status as following:

# kubectl get sts -n aaa
test111       0/3     91m

but Kubesphere Console will show 1/3

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.: