claudio4j commented on PR #4121: URL: https://github.com/apache/camel-k/pull/4121#issuecomment-1466057555
> we should have the same result by providing certain dependencies and a series of built-time properties. At the end of the day, a trait is just syntactic sugar That's true. Not having the master trait, the required actions the user must perform: - provide the required dependencies with `-d camel:<component name>` - [set the rbac permissions for the ServiceAccount](https://github.com/apache/camel-k/tree/main/resources/addons/master) to handle either `Lease` or `ConfigMap` The traits automation in general help users to deal with the boring setup, I would say this automation is good for camel K, at the cost of having the coupling you mentioned. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
