wuyingjun

Maybe we can set the status in default interpreter but how to set the spec field ?

cc @RainbowMango

> > Maybe we can set the status in default interpreter but how to set the spec field ? > > What about propagating the PVC to more than one...

> That's the point, we can't set two names to a single filed. That's the limitation. Even for status, we still got similar situations. If we do not use override...

/assign

/cc @RainbowMango @XiShanYongYe-Chang @chaunceyjiang

It seems the `newOverridePolicyFunc` prevent the binding_controller reconcile, Can we modify here?

> apiVersion: policy.karmada.io/v1alpha1 > kind: OverridePolicy > metadata: > name: busybox-overridepolicy1 > namespace: default > spec: > > overrideRules: > - targetCluster: > clusterNames: > - cluster30 > overriders: >...

> The rbs may not be matched. We can add some logs for debugging: > > https://github.com/karmada-io/karmada/blob/e6e946ff51ecca5cbb7d8c0e9931b559e44313e9/pkg/controllers/binding/binding_controller.go#L261 `1` I create deployment `2` I create op with nil resource selector in...

我们的环境出现的问题情况 就是 如果 op的 resourceselector 是空的 ，当你创建这个op的时候，他无法触发binding_controller 的调和。 但是 按照 op的接口设计 resourceselector 为空应该是match 这个 ns下 所有的。 只有 在 binding_controller的因为 resourcebinding 或者其他资源调和 之前 这个 带有 空的 resourceselector 的 op 已经被应用了，他才会应用成功。 不知道我是否理解和描述的有问题。