Unable to install multiple Camel K operators using Helm due to ClusterRole ownership conflict

[Drunkpuppy16]

What happened?

I'm trying to install multiple Camel K operators in different namespaces using Helm, but I encounter an error related to ClusterRole ownership metadata.

Setup:
operator.global=false

operator.operatorId is set to different values per namespace

Each operator is installed into its own namespace (camel1, camel2, etc.)

Installation is done using the Helm chart

Error: INSTALLATION FAILED: Unable to continue with install: ClusterRole "camel-k-edit" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "camel2": current value is "camel1"
Notes:
The first installation in namespace camel1 succeeds.

Any subsequent installation in a different namespace fails due to ClusterRole "camel-k-edit" already existing, with annotations pointing to the initial release.

Expected Behavior:
Helm should allow multiple operator installations in different namespaces without conflicting on global ClusterRole resources like camel-k-edit.

Steps to reproduce

No response

Relevant log output

Camel K version

v2.6.0

[squakez]

Thanks for reporting. Feel free to have a look and contribute to the fix.