Problems with LabelsOverrider

[guozheng-shen]

Please provide an in-depth description of the question you have:
When we use Karmada to propagate Deployments、StatefulSets to member clusters, I want to add a label <cluster: {memberCluster}> to our resources. But labelsOverrider only supports adding a certain value. What can I do.

What do you think about this question?:
Can we use an expression like ${.memberCluster}, and let Karmada auto inject the real value into the label?

Environment:

• Karmada version: 1.19
• Kubernetes version: 1.28
• Others:

[RainbowMango]

Why do you have to label your resources with a dynamic cluster name?

Karmada version: 1.19

By the way, Karmada hasn't released v1.19 yet.

[guozheng-shen]

Why do you have to label your resources with a dynamic cluster name?

Karmada version: 1.19

By the way, Karmada hasn't released v1.19 yet.

sorry, version is 1.9

[guozheng-shen]

Why do you have to label your resources with a dynamic cluster name?

Karmada version: 1.19

By the way, Karmada hasn't released v1.19 yet.

other systems need get member cluster from label

[RainbowMango]

Sorry, I still don't get the use case like why the other systems needs the member cluster, and what they do with these cluster names.

[guozheng-shen]

Sorry, I still don't get the use case like why the other systems needs the member cluster, and what they do with these cluster names.

For example, we need to synchronize our instance info to our name service and cmdb. The instance info needs a cluster name. All of our existing processes are implemented through labels. If we want to make modifications, it requires cooperation from other teams, and it's difficult.

[guozheng-shen]

we are going to use webhooks to achieve the goal

[guozheng-shen]

Thanks @RainbowMango

[RainbowMango]

By the way, are you using Karmada now?

[guozheng-shen]

By the way, are you using Karmada now?

Yes, this is our arch https://github.com/karmada - io/karmada/issues/5103. Each region contains two or more karmada clusters for ha. However, only the specified ca-cert and ca-key have a small problem when monitoring. We need to add the --service - account-key-file={other karmada cluster karmada.key} flag in the karmada-apiserver start command. if not the Prometheus agent will get a 401 error when collecting metrics

[RainbowMango]

Great! Glad to hear from you. May I know your company name? Is it presented on the Adopter list? https://karmada.io/adopters

[guozheng-shen]

Tongcheng Travel, It's inside.

[RainbowMango]

OK. You are welcome to join the Adopter Group, you can get more details on the linked doc.