After upgrade to release v0.5.0, the installer times-out waiting for the eventing-controller deployment. After further investigation, the operator seems to run under the knative-eventing-operator service account.
Example error in the Eventing operator pod logs, after current installer runs on a fresh minishift:
clusterroles.rbac.authorization.k8s.io "addressable-resolver" is forbidden: must have cluster-admin privileges to use the aggregationRule"
This change gives cluster-admin to the knative-eventing-operator service account.
Thanks for this, but I believe with the latest eventing operator changes, this shouldn't be necessary. We stopped using the operator's SA for the installed eventing components.
After upgrade to release v0.5.0, the installer times-out waiting for the
eventing-controller
deployment. After further investigation, the operator seems to run under theknative-eventing-operator
service account.Example error in the Eventing operator pod logs, after current installer runs on a fresh minishift:
clusterroles.rbac.authorization.k8s.io "addressable-resolver" is forbidden: must have cluster-admin privileges to use the aggregationRule"
This change gives cluster-admin to the
knative-eventing-operator
service account.