REQUEST: New repo for building fleet-apiserver about community

[XiShanYongYe-Chang]

/assign @kevin-wangzefeng

[kevin-wangzefeng]

I think it is better to keep the repo name as kubernetes and not change it to fleet-apiserver.
The forked repo should only contain the necessary inline changes to make the kube-apiserver programmable for the fleet-apiserver development.
The rest of the fleet-apiserver code should be stored in a separate place, maybe a staging repo in karmada-io/karmada or a stand-alone repo.

[XiShanYongYe-Chang]

I think it is better to keep the repo name as kubernetes and not change it to fleet-apiserver.

Thanks, I get it. I will update the issue description.

The forked repo should only contain the necessary inline changes to make the kube-apiserver programmable for the fleet-apiserver development.
The rest of the fleet-apiserver code should be stored in a separate place, maybe a staging repo in karmada-io/karmada or a stand-alone repo.

Yes, we will strive to develop and iterate according to this strategy. The plan is to first write code for the fleet-apiserver component and deploy it in the karmada-io/karmada repository.

[XiShanYongYe-Chang]

Revised the description of the issue.

[kevin-wangzefeng]

The plan is to first write code for the fleet-apiserver component and deploy it in the karmada-io/karmada repository.

I'm not quite clear on this, could you rephrase it?

[XiShanYongYe-Chang]

I'm sorry, I didn't explain it clearly. Let me try to describe it more clearly.

We plan to first store the rest of fleet-apiserver code in the karmada-io/karmada repo and compile and deploy fleet-apiserver. If this cannot be achieved, we will consider handling this matter in a new repository.

[kevin-wangzefeng]

Thanks for the clarification, the fork repo has been created at: https://github.com/karmada-io/kubernetes

[RainbowMango]

Just created v1.28.4-karmada branch based on Kubernetes v1.28.4.

[XiShanYongYe-Chang]

Thanks~ @kevin-wangzefeng @RainbowMango
/close

[karmada-bot]

@XiShanYongYe-Chang: Closing this issue.

In response to this:

Thanks~ @kevin-wangzefeng @RainbowMango
/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.