[Umbrella] Use permanent-id to replace namespace/name labels in the resource

[XiShanYongYe-Chang]

What would you like to be added:

Please ref to https://github.com/karmada-io/karmada/issues/4683#issuecomment-1996604867

Why is this needed:

Continue the work of #4000 and break down the tasks to be done.

• [ ] Unify and add permanent-id labels to PropagationPolicy/ClusterPropagationPolicy, ResourceBinding/ClusterResourceBinding, and Work resources in karmada-webhook.
  • [x] Add permanent-id for pp, cpp, rb, crb, work in the karmada-webhook @jwcesign @XiShanYongYe-Chang #4474
  • [ ] Remove the add permanent-id logic in the karmada-controller-manager (we can do it in the next release) @whitewindmills
  • [x] For Work resource #4928
  • [ ] For RB/CRB resource #4950
  • [ ] For PP/CPP resource #4949
• [x] Replace the use of namespace/name labels in the code with permanent-id labels, including: @whitewindmills @XiShanYongYe-Chang
  • [x] propagationpolicy.karmada.io/namespace, propagationpolicy.karmada.io/name -> propagationpolicy.karmada.io/permanent-id #4743
  • [x] clusterpropagationpolicy.karmada.io/name -> clusterpropagationpolicy.karmada.io/permanent-id #4743
  • [x] resourcebinding.karmada.io/key -> resourcebinding.karmada.io/permanent-id #4811
  • [x] clusterresourcebinding.karmada.io/key -> clusterresourcebinding.karmada.io/permanent-id #4811
  • [x] work.karmada.io/namespace, work.karmada.io/name -> work.karmada.io/permanent-id #4813 #4765 #4865
• [x] Clean up the uid labels on the resource: @liangyuanpeng #4718
  • [x] propagationpolicy.karmada.io/uid
  • [x] clusterpropagationpolicy.karmada.io/uid
  • [x] resourcebinding.karmada.io/uid
  • [x] clusterresourcebinding.karmada.io/uid
  • [x] work.karmada.io/uid
• [x] Deprecated namespace/name labels on resources: @whitewindmills
  • [x] Deprecated propagationpolicy.karmada.io/namespace #4743
  • [x] Deprecated propagationpolicy.karmada.io/name #4743
  • [x] Deprecated clusterpropagationpolicy.karmada.io/name #4743
  • [x] resourcebinding.karmada.io/key #4811
  • [x] clusterresourcebinding.karmada.io/key #4811
  • [x] work.karmada.io/namespace #4813
  • [x] work.karmada.io/name #4813
• [ ] Remove those labels: propagationpolicy.karmada.io/namespace, propagationpolicy.karmada.io/name
• [ ] The names of PP and CPP are not allowed to exceed 63 characters. This is the verification logic of karmada-webhook: https://github.com/karmada-io/karmada/blob/9822d099d1b717902003b2c7a11448d2cea6ac05/pkg/webhook/propagationpolicy/mutating.go#L74-L76 The reason for adding this verification is that the names of PP and CPP will appear in In the resource template and the label value of RB, this check can be removed after we solve the issue.
• [ ] Describe the impact of the current task on users and upgrade precautions in the upgrade document.

[liangyuanpeng]

I'm interested in this and I want to take care of Clean up the uid labels on the resource And do we plan to issue deprecation warnings to users before removing logic?

[XiShanYongYe-Chang]

I'm interested in this and I want to take care of Clean up the uid labels on the resource.

Thanks a lot~

And do we plan to issue deprecation warnings to users before removing logic?

I think it is necessary, although we have mentioned the need to discard these labels in many community meetings and related issue descriptions and discussions, we still need to find a clear place to describe the text, so that this information can be passed to more users.

Do you have any suggestions?

[XiShanYongYe-Chang]

/help Anyone interested can pick up the task to develop.

[karmada-bot]

@XiShanYongYe-Chang: This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/karmada-io/karmada/issues/4711): >/help >Anyone interested can pick up the task to develop. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[whitewindmills]

I wanna pick up this one Clean up namespace/name labels on resources.

[XiShanYongYe-Chang]

I wanna pick up this one Clean up namespace/name labels on resources.

Ok, thx~

[liangyuanpeng]

I think it is necessary, although we have mentioned the need to discard these labels in many community meetings and related issue descriptions and discussions, we still need to find a clear place to describe the text, so that this information can be passed to more users. Do you have any suggestions?

Is FeatureGates enough? At least it gives users a chance to be compatible., like :

  //**TODO GA in 1.11, delete the FeatureGate**
 if !FeatureGates.xxx.enabled {
        // TODO: Delete following two lines in release-1.9
    delete(bindingCopy.Labels, workv1alpha2.ResourceBindingUIDLabel)
    delete(bindingCopy.Labels, policyv1alpha1.PropagationPolicyUIDLabel)
 }

cc @chaunceyjiang

[yizhang-zen]

@chaunceyjiang , it seems all the tasks have been picked up. Any input from you and any work that need us?

[XiShanYongYe-Chang]

/assign @liangyuanpeng @whitewindmills @XiShanYongYe-Chang