astefanutti commented on a change in pull request #2711:
URL: https://github.com/apache/camel-k/pull/2711#discussion_r792413705
##########
File path: config/rbac/kustomization.yaml
##########
@@ -25,6 +25,7 @@ resources:
- user-cluster-role.yaml
- operator-role-events.yaml
- operator-role-knative.yaml
+- operator-role-olm.yaml
Review comment:
We aim to keep the set of permissions for the operator reduced to the
minimum. Extra permissions for OLM resources are not needed by the operator,
only by the account that's used to run the Kamel CLI install command. In the
Tekton test case, it seems the problem is two folds:
* The test re-use the `camel-k-operator` ServiceAccount, while it should
create one dedicated to calling the Kamel CLI,
* The test runs the install command, but I doubt it's a real use case.
Usually, Tekton pipelines would run integrations, not install Camel K.
They are some documentation available at
https://camel.apache.org/camel-k/1.8.x/tutorials/tekton/tekton.html. That being
said, I doubt this feature has ever been actually used.
--
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]
