[Bug]: app.kubernetes.io/name should be changed to customized name

[nsettipa]

Bug Description

Hi,

we are planning to change label app.kubernetes.io/name for Kafka, cruise-control and mirror maker 2. Not able to change it.
we tried to set new label name such as product-kafka-release... It is not getting changed.

Is there way to change label name while creating Pod spec. Tried all possibilities and could not change it for these micro-services.

k describe pod cluster-b-kafka-0 -n dualstack2
Name: cluster-b-kafka-0
Namespace: dualstack2
Priority: 0
Node: node-10-158-153-79/10.158.153.79
Start Time: Mon, 13 Jan 2025 16:02:07 +0100
Labels: app.kubernetes.io/instance=cluster-b
app.kubernetes.io/managed-by=strimzi-cluster-operator
app.kubernetes.io/name=kafka

As you see, label name kafka is not getting changed through yaml file changes or through while Pod creation.

Please kindly suggest on this.

Rgds,
Narasimham

Steps to reproduce

No response

Expected behavior

we would like to change meta-data label name: app.kubernetes.io/name to specific product name to reflect for the purpose we are using.

Strimzi version

0.36

Kubernetes version

Kubernetes 1.30

Installation method

No response

Infrastructure

No response

Configuration files and logs

No response

Additional context

No response

[scholzj]

I have the feeling that this was discussed and rejected many times in the past already? These labels are pretty messy as they lack proper specification how they are supposed to work / be used. As a result, everyone expects them to work differently. And we cannot make them work in 5 different ways to make everyone happy. Sorry.

[nsettipa]

Hi We cannot customize or change these labels. Thank you. Rgds, Narasimham

…

On Mon, 13 Jan, 2025, 20:50 Jakub Scholz, ***@***.***> wrote: I have the feeling that this was discussed and rejected many times in the past already? These labels are pretty messy as they lack proper specification how they are supposed to work / be used. As a result, everyone expects them to work differently. And we cannot make them work in 5 different ways to make everyone happy. Sorry. — Reply to this email directly, view it on GitHub <#11029 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7EJS25XOL5MZX4Z3OOSJL2KPKUPAVCNFSM6AAAAABVC2PNL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXGQYDCOJUHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ppatierno]

Triaged on 23.1.2025: closing because they cannot be changed and we have to stick with the current implementation.