squakez opened a new issue, #3725: URL: https://github.com/apache/camel-k/issues/3725
I've noticed that if we run an Integration without the `camel.apache.org/operator.id` annotation, then, the behavior is to use the namespace operator where this is stored. However, when we `kamel run/bind`, there is a forced setting to `camel.apache.org/operator.id: camel-k` that may interfere when a user is interested in getting the Integration back (ie `-o yaml`) and later pushing the Integration to the cluster in any given namespace. Should we remove the presence of default `operator.id: camel-k`? is there any particular reason why we want to leave it there @christophd ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
