Replies: 2 comments 9 replies
-
@jesumyip - in your function worker config, do you have This appears to be documented here: https://pulsar.apache.org/docs/next/functions-worker-run-separately/#enable-tls-encryption. Here are some of the relevant code references: (A couple skipped references, but it's easy to follow in an IDE.) |
Beta Was this translation helpful? Give feedback.
-
What version of Pulsar are you using? I'm getting the same error with pulsar-admin. I'm not in kubernetes but bare metal. For me this only effects Pulsar 2.9.3. I had no problem with pulsar-admin with either 2.9.2 or 2.10.2 connecting to the same broker. |
Beta Was this translation helpful? Give feedback.
-
I'm getting an OpenSSLEngine general error in my pulsar function pods. I've narrowed it down to pulsar-admin that's causing this issue. We use cert-manager to secure our Pulsar instance.
Everytime I run pulsar-admin manually to create a function, I understand that this causes Pulsar to create a K8s manifest that deploys a pod to run my function. When I inspect the created pod, I see that it's got a few issues.
Sorry for the basic questions as we are completely new to Pulsar.
Beta Was this translation helpful? Give feedback.
All reactions