[GitHub] [camel-k] astefanutti commented on issue #2950: camel-k-operator forbidden to get kafkachannels.messaging.knative.dev since 1.8.x

[GitBox <gi...@apache.org>]

astefanutti commented on issue #2950:
URL: https://github.com/apache/camel-k/issues/2950#issuecomment-1022458278


   Wildcard permissions have been removed with #2807, as unbounded RBAC is not considered a best practice.
   
   A Knative Sink can be any resource that's Addressable, and the Camel K operator do a GET request to retrieve the address from the resource `status.address.url` field.
   
   We can expand the list of default Addressable resources that the operator is granted read permission on, like `KafkaChannel`, but that's ultimately the admin responsibility to set these extra permissions in the `camel-k-operator` Role, similar to what Knative requires with the `kafkasinks-addressable-resolver` ClusterRole:
   
   https://knative.dev/docs/eventing/sinks/#using-custom-resources-as-sinks
   
   If that is the right approach, we need to document it. 
   


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org