fix deployment replicas syncer in case that status.replicas haven't been collected from member cluster to template

[chaosi-zju]

What type of PR is this?

/kind bug

What this PR does / why we need it:

This PR mainly handles two problem:

1、Problem 1

we should make sure the latest collected status.replicas is synced from binding to template.

e.g: user set deployment.spec.replicas = 2, then sum replicas in binding.status becomes 2, however, if now deployment.status.replicas is still 1, we shouldn't update spec.replicas to 1 until status.replicas becomes 2.

2、Problem 2

as described in #4758, fix deployment replicas syncer in case that the status.replicas in aggregatedStatus of binding is 0.

actually, if member cluster deployment is controlled by hpa, its status.replicas must > 0 (since hpa.minReplicas > 0),

so, if its status.replicas is 0, means the status haven't been collected from member cluster, and needs waiting before do the following update.

Which issue(s) this PR fixes:

Fixes #4758

Special notes for your reviewer:

bugfix for #4707

Does this PR introduce a user-facing change?:

fix deployment replicas syncer in case that `status.replicas` haven't been collected from member cluster to template.

[chaosi-zju]

@XiShanYongYe-Chang @chaunceyjiang can you review on this? thanks very much for your precious time!

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 51.77%. Comparing base (dbb82be) to head (7bcb400).
Report is 23 commits behind head on master.

Files	Patch %	Lines
...esourceinterpreter/default/native/reflectstatus.go	0.00%	11 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4729      +/-   ##
==========================================
- Coverage   51.78%   51.77%   -0.02%     
==========================================
  Files         250      250              
  Lines       25000    24993       -7     
==========================================
- Hits        12947    12940       -7     
  Misses      11343    11343              
  Partials      710      710              

Flag	Coverage Δ
unittests	51.77% <0.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[liangyuanpeng]

/kind flake

[XiShanYongYe-Chang]

/lgtm

[chaosi-zju]

the max backoff time of workqueue is 1000s @RainbowMango

karmada/pkg/sharedcli/ratelimiterflag/ratelimiterflag.go

Lines 42 to 48 in 13dafc6

	// AddFlags adds flags to the specified FlagSet.
	func (o *Options) AddFlags(fs *pflag.FlagSet) {
	fs.DurationVar(&o.RateLimiterBaseDelay, "rate-limiter-base-delay", 5*time.Millisecond, "The base delay for rate limiter.")
	fs.DurationVar(&o.RateLimiterMaxDelay, "rate-limiter-max-delay", 1000*time.Second, "The max delay for rate limiter.")
	fs.IntVar(&o.RateLimiterQPS, "rate-limiter-qps", 10, "The QPS for rate limier.")
	fs.IntVar(&o.RateLimiterBucketSize, "rate-limiter-bucket-size", 100, "The bucket size for rate limier.")
	}

karmada/vendor/k8s.io/client-go/util/workqueue/default_rate_limiters.go

Lines 37 to 45 in 13dafc6

	// DefaultControllerRateLimiter is a no-arg constructor for a default rate limiter for a workqueue. It has
	// both overall and per-item rate limiting. The overall is a token bucket and the per-item is exponential
	func DefaultControllerRateLimiter() RateLimiter {
	return NewMaxOfRateLimiter(
	NewItemExponentialFailureRateLimiter(5*time.Millisecond, 1000*time.Second),
	// 10 qps, 100 bucket size. This is only for retry speed and its only the overall factor (not per item)
	&BucketRateLimiter{Limiter: rate.NewLimiter(rate.Limit(10), 100)},
	)
	}

[chaunceyjiang]

the max backoff time of workqueue is 1000s

The resource key should be able to re-queue infinitely many times, it's just that the maximum allowed backoff time is 1000s.

[RainbowMango]

/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/controllers/OWNERS [RainbowMango]
• pkg/resourceinterpreter/OWNERS [RainbowMango]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[RainbowMango]

/lgtm