You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.
For example, in #48 the Receive Adapter which connects to the k8s API server, it needs permissions to be able to watch for events. Currently the Deployment created by KubernetesEventSource (and because it uses ContainerSource) runs as the default service account:
serviceAccount: default
serviceAccountName: default
That means that the user needs to grant this account permissions to watch for k8s events which is undesirable. It would be better to be able to specify the Service Account that should be used so that it can be RBAC'd appropriately.
Actual Behavior
Doesn't work unless you grant rights to default/default ServiceAccount
Steps to Reproduce the Problem
Create KubernetesEventSource or ContainerSource and watch
Observe the Deployment / Pods created
See they run as default service account.
Additional Info
duck for namespaceable? :)
The text was updated successfully, but these errors were encountered:
Expected Behavior
For example, in #48 the Receive Adapter which connects to the k8s API server, it needs permissions to be able to watch for events. Currently the Deployment created by KubernetesEventSource (and because it uses ContainerSource) runs as the default service account:
serviceAccount: default
serviceAccountName: default
That means that the user needs to grant this account permissions to watch for k8s events which is undesirable. It would be better to be able to specify the Service Account that should be used so that it can be RBAC'd appropriately.
Actual Behavior
Doesn't work unless you grant rights to default/default ServiceAccount
Steps to Reproduce the Problem
Additional Info
duck for namespaceable? :)
The text was updated successfully, but these errors were encountered: