-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Reading Functions Worker ConfigMap #56
Comments
Sadly this error still persists even in 2.7 |
…lume config for bookie (apache#56) * helm changes for ebs logs * helm changes for ebs logs * helm changes broker for ebs logs * helm changes broker for ebs logs * helm changes broker for ebs logs * helm changes broker for ebs logs * helm changes broker for ebs logs * helm changes broker for ebs logs * helm changes broker for ebs logs * helm changes broker for ebs logs * adding storage class for broker * adding storage class for broker * logs name change and storage class removal * multi volume modification for book keeper * multi volume modification for book keeper
the functions-worker-config map is a feature which doesn't work at all. it is explained at #392 (comment) . I'm going to fix this issue by removing the pulsar-function-worker-config map since it's just causing confusion and doesn't work. |
Describe the bug
When enabling functions, the broker throws the following error:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I think the role needs to be bound to the broker service account. It currently creates another service account named
pulsar-functions-worker
. Not sure if that SA is used by the functions, but thepulsar-broker-acct
does not have access to the function worker config map.What is the
pulsar-functions-worker
used for? Is it used by the functions? If so we can add read access to thepulsar-broker-acct
role that is bound so it can read the ConfigMap.The text was updated successfully, but these errors were encountered: