Hongcai Ren

First, Karmada now using `/readyz` to detect the cluster healthy, and will back off to `healthz` in case of no response from `/readyz`. I remember `/readyz` will be several checks....

Sorry for the slow response, I just got time to dig into this issue. > It seems both readyz and healthz act the same, and nearly always returns ok, if...

The reason why I insist on investigating what exactly checks have been done by `/readyz` is I want to figure out the gap between what we have and user expectations....

@tedli @Poor12 @jwcesign @chaunceyjiang any comments? I think this feature might be an important extension capability for Karmada, it might be used to enhance the cluster failover functionality.

I'm trying to figure out which PR/Issue should be included in the coming v1.7 release which is planned at the end of this month. I guess we don't have enough...

> Through the definition of Work Manifest spec.strategy.canary.steps, it is found that the type of 'object'{} has changed to 'array'[], which does not conform to the original type definition, so...

> use argo rollout， install crd and sample reference: https://argo-rollouts.readthedocs.io/en/stable/installation/ https://argo-rollouts.readthedocs.io/en/stable/features/canary/ Which version of `argo-rollouts` are you using? I'm trying to reproduce it on my side.

I tried to reproduce it on my side against `Karmada v1.5.0`, it works well, here is my operations: - launch the testing environment by `hack/local-up-karmada.sh` based on Karmada v1.5.0. -...

I still can't reproduce with the `replicaScheduling`: ```yaml apiVersion: policy.karmada.io/v1alpha1 kind: PropagationPolicy metadata: name: nginx-propagation spec: resourceSelectors: - apiVersion: argoproj.io/v1alpha1 kind: Rollout name: nginx-rollout placement: replicaScheduling: replicaDivisionPreference: Weighted replicaSchedulingType: Divided...

> image: registry.aliyuncs.com/google_containers/kube-apiserver:v1.20.8 I see you are using `kube-apiserver:v1.20.8` (I'm using `image: registry.k8s.io/kube-apiserver:v1.25.2`). Please check if the `.spec.strategy.canary.steps` changed on Karmada apiserver.