-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
flowchartsman/pulsar
#6Labels
area/functiontype/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug
Description
Search before asking
- I searched in the issues and found nothing similar.
Version
After enabling JWT auth on our cluster, all of our Go functions started failing. This is because authentication information is only passed to the pulsar-admin command, and also because the Go function SDK has no concept of auth providers.
Minimal reproduce step
Just enable auth, and watch your go functions start to complain:
broker.pulsar.svc.cluster.local:6650 local_addr=172.27.168.187:37436
2023/06/01 03:05:16.139 connection.go:226: [warning] Failed to establish connection with broker: 'Unable to authenticate' remote_addr=pulsar://pulsar-broker.pulsar.svc.cluster.local:6650 local_addr=172.27.168.187:37436
2023/06/01 03:05:45.027 log.go:77: [error] create producer error:connection error
2023/06/01 03:05:45.027 instance.go:210: [fatal] connection error
Stream closed EOF for pulsar/pf-public-default-function-test-30-c169f141-0 (pulsarfunction)
What did you expect to see?
Working functions.
What did you see instead?
Dead functions.
Anything else?
No response
Are you willing to submit a PR?
- I'm willing to submit a PR!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/functiontype/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug