-
Notifications
You must be signed in to change notification settings - Fork 630
[BUG] Source Controller Service Account #1326
Copy link
Copy link
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/good-first-issueDenotes an issue ready for a new contributor.Denotes an issue ready for a new contributor.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/good-first-issueDenotes an issue ready for a new contributor.Denotes an issue ready for a new contributor.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Describe the bug
The Eventing Source Controller uses the same ServiceAccount,
eventing-controller, as the core Eventing Controller. According to Eventing's Service Account docs, they must be different.Expected behavior
The Eventing Controller and the Eventing Sources Controller should use different Kubernetes ServiceAccounts, so that they can each be given minimal RBAC permissions, rather than the union of permissions needed for both.