astefanutti opened a new issue #1632: URL: https://github.com/apache/camel-k/issues/1632
In some environments, where Camel K is delivered as a managed service, it would be useful to control the ability to configure the Camel K resources at the fields level based on RBAC, and restrict the configuration surface for users, to keep the risk of mis-configuration and the operation effort low. This would be particularly useful for build related fields, whose mis-configuration and combinatory complexity can lead to some hard to troubleshoot errors. From the implementation standpoint, a validating admission webhook could be exposed by the operator, to gate the creation and updates of Camel K resources. The Webhook could rely on the `userInfo` field from the `AdmissionReview` request, and check whether the content of the `.Spec` field for the Camel K resource does not contain forbidden fields. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
