karmada icon indicating copy to clipboard operation
karmada copied to clipboard

Karmada can not get the pvc information include status and spec

Open wuyingjun-lucky opened this issue 2 years ago • 7 comments

What would you like to be added: Karmada can get the pvc information include status and spec Why is this needed: 1 pvc is dispatched by karmada control plane 2 member cluster by kubectl : image 3 host cluster by kubectl: image

wuyingjun-lucky avatar Oct 14 '22 03:10 wuyingjun-lucky

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

wuyingjun-lucky avatar Oct 14 '22 03:10 wuyingjun-lucky

cc @RainbowMango

wuyingjun-lucky avatar Oct 14 '22 03:10 wuyingjun-lucky

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 cluster? We would get one volume name or more?

RainbowMango avatar Oct 14 '22 06:10 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 cluster? We would get one volume name or more?

Both situations will exist

wuyingjun-lucky avatar Oct 14 '22 06:10 wuyingjun-lucky

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.

RainbowMango avatar Oct 14 '22 06:10 RainbowMango

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 policy, the capacity or accessModes will keep the same. Do you think we can just keep the fields unchanged.

wuyingjun-lucky avatar Oct 14 '22 06:10 wuyingjun-lucky

If we do not use override policy, the capacity or accessModes will keep the same. Do you think we can just keep the fields unchanged.

I guess the .spec.volumeName and .status.accessModes are both generated by member clusters, right? Then, I don't think we can sync the status back to the resource template without bringing ambiguity.

RainbowMango avatar Oct 14 '22 06:10 RainbowMango

As a lack of activity, let's close this first, feel free to reopen it if you still need it. /close

XiShanYongYe-Chang avatar Mar 04 '24 02:03 XiShanYongYe-Chang

@XiShanYongYe-Chang: Closing this issue.

In response to this:

As a lack of activity, let's close this first, feel free to reopen it if you still need it. /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

karmada-bot avatar Mar 04 '24 02:03 karmada-bot