Let karmada cluster sync CRD from member clusters

[vincent-pli]

What would you like to be added:
Let Karmada cluster sync CRD from member cluster

Why is this needed:
Karmada cluster will create template and sync to member cluster, that's great.
but for CRD scenario, if there is no such CRD in the karmada cluster but has installed in the member cluster, that is a mass that user need apply such CRDs both in karmada cluster and member cluster.

[RainbowMango]

That might be an interesting feature. Can we have a chat about this in next week's meeting?

[GitHubxsy]

Sounds cool.

[vincent-pli]

Sure, thanks @RainbowMango

[mrlihanbo]

Sounds cool. Need to consider the scenario of pull mode cluster

[RainbowMango]

Sure, thanks @RainbowMango

@vincent-pli I haven't seen the agenda on today's meeting.

[vincent-pli]

Missing the meeting, block by a full day tough training, sorry for that @RainbowMango

[RainbowMango]

No worries. We can still discuss this here.

[pigletfly]

Brilliant idea.I think we can provide a field to tell karmada if there is a existed workload in member cluster, should it be adopted or just leave it alone.

[RainbowMango]

Hi @vincent-pli Looking forward to meeting you at the community meeting and talking about this feature there. I'm sure it would be a wonderful feature.

[merryzhou]

hi，I am also interested in this feature, any news？

[RainbowMango]

Hi @merryzhou
No, if I remember right, we haven't discussed it yet. I don't know if @vincent-pli is still interested in this topic.

@merryzhou maybe you can lead the effort to move this forward. I get your back.

My idea is to provide a controller (just like the namespace controller) to propagate the CRD to member clusters automatically.

By the way, I'm preparing the draft roadmap of 2022, this feature will be included there.

[merryzhou]

@merryzhou maybe you can lead the effort to move this forward

ok, I'd like to have a try.

My idea is to provide a controller (just like the namespace controller) to propagate the CRD to member clusters automatically.

I think this issue is about sync CRD from member clusters, not propagate the CRD to member clusters?

[RainbowMango]

I think this issue is about sync CRD from member clusters, not propagate the CRD to member clusters?

I have a different opinion. Sync CRD from Karmada to member clusters should have higher priority at least.

If the CRD resources are already in the member clusters, they only need to sync once( to Karmada), I can't see much pain from that.

[merryzhou]

Sync CRD from Karmada to member clusters should have higher priority at least.

we can open a new issue about this。

[RainbowMango]

I'm going to close this as its lacks activities for a long time.

Please feel free to re-open it if anyone thinks it is needed.

/close

[karmada-bot]

@RainbowMango: Closing this issue.

In response to this:

I'm going to close this as its lacks activities for a long time.

Please feel free to re-open it if anyone thinks it is needed.

/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.