chaosi-zju

It seems like there are four ways to achieve it: 1. add `--skipped-propagating-apis` as params of `karmada-controller-manager`: API is not intuitive to users、lack of management、lack of visualization 2. managed as...

> I was wondering where should I add these tests. Should I add them in the `propogationpolicy_test.go`? Or should I create a new file like `lazy_activation_policy_test.go`? Hi @Affan-7, sorry for...

> I can work on `Simple Case 1`. Okey, your great effort will provide a important example to followers~ Looking forward to your PR~ Feel free to ask me if...

> Can I work on this? @ewon78 Hi, of course you can~ which cases would you prefer?

Ok, thank you for your enthusiasm @zhzhuang-zju @ewon78 ~ Besides, since another friend `Affan-7` has submited a PR #4622 which haven't been merged, please be careful not to have too...

> can you please assign me some more test cases? ok, of course, please just wait for a while~

@Affan-7 hi, Does [Combined Case 3] fit for you?

@ikaven1024 hello, do you have time to help take a look at this problem? Thank you very much~

> Does it solve this issue #3617? Hi @ikaven1024, it seems that it is the same problem as #3617~ And, I have tested that this PR can also solve #3617...

I find a unsatisfied case. 1. Apply `Rollout` CRDs on both Karmada APIserver and member1 as per https://argo-rollouts.readthedocs.io/en/stable/installation/#controller-installation. 2. Apply a `ResourceInterpreterCustomization` to Karmada APIserver. ```yaml apiVersion: config.karmada.io/v1alpha1 kind: ResourceInterpreterCustomization...