[Bug]: Child Chart CRD Instance Label Conflicts with ArgoCD

[jacob-kuder]

What happened?

We are using Helm charts to deploy jaeger-operator to an AWS EKS cluster, integrated with ArgoCD. When deployed, the application comes up fully synced and healthy, minus a "Shared Resource Warning" in the ArgoCD UI for our jaeger tool. To resolve the warning, we had to remove the app.kubernetes.io/instance: jaeger-operator label from the CRD that was included in the Helm charts. This made the warning in ArgoCD disappear with no seen issues to the tool's functionality/health. We'd like to inquire why that label might be needed and, if it is needed, possibly provide a workaround for our use case.

Please see screenshots below showing the ArgoCD warning specifically.

Thank you for your time and help!

Steps to reproduce

1. Deploy the jaeger-operator into a Kubernetes cluster (AWS EKS is what we use) and utilizing ArgoCD
2. Ensure the application comes up successfully (healthy and fully synced)
3. Review any warnings/errors via the ArgoCD UI

Expected behavior

Not throw shared resource warnings when nothing is actually being shared

Relevant log output

No response

Screenshot

Additional context

No response

Jaeger backend version

v1.47.0

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

Linux

Deployment model

Kubernetes

Deployment configs

No response