lburgazzoli commented on issue #4535: URL: https://github.com/apache/camel-k/issues/4535#issuecomment-1622309171
I'm not sure about that is a good idea and I'm quite reluctant to add tooling specific field to the spec of Binding/Pieps/Integration as that has no value for the controller but still, if you change them, then the generation of the resource changes indicating that a reconcile loop should take place so it seems semantically incorrect to me especially as a binding/pipe/integration, as opposed to a Kamelet, results int a running POD and a change to the spec could lead to some disruption or in any case to some additional work for the controller without a clear benefit as opposed to use annotations. I also don't see the pattern to add tooling specific field to specs which should be keep as minimal as possible and even Kubernetes uses annotation for some kind of tooling related stuffs (i.e. `kubectl.kubernetes.io/last-applied-configuration`). So of course fields can be added but IMHO, it should be the very very last option. -- 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]
