Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't use KubernetesRuntimeFactory because it doesn't work #157

Open
pgier opened this issue Sep 8, 2023 · 2 comments
Open

Don't use KubernetesRuntimeFactory because it doesn't work #157

pgier opened this issue Sep 8, 2023 · 2 comments
Labels
high priority

Comments

@pgier
Copy link
Collaborator

pgier commented Sep 8, 2023 •
edited
Loading

Currently the operator set this in functions_worker.conf by default. This should not be set because it doesn't work.

functionRuntimeFactoryClassName: org.apache.pulsar.functions.runtime.kubernetes.KubernetesRuntimeFactory

The problem is that when this is enabled, it causes an incorrect pulsar admin url to be used in the generated connector pod.

Related: apache/pulsar#9213
@nicoloboschi
Copy link
Contributor

@pgier that problem has been resolved in Pulsar 2.8.
do you still have the issue?

@pgier
Copy link
Collaborator Author

pgier commented Feb 1, 2024 •
edited
Loading

Yes, I experienced this issue in 2.10. I didn't test with other versions.
The workaround was to manually set functionRuntimeFactoryClassName to an empty string.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
high priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pgier @nicoloboschi