-
Notifications
You must be signed in to change notification settings - Fork 227
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
Brokers fail starting on GKE Autopilot #416
Comments
@theoribeiro Does this happen also with the most recent Helm chart release 3.1.0 ? |
@lhotari yes, I just updated the chart to test it after seeing the announcement on Slack |
The stack traces reference Pulsar 2.10.2 version which is the default for chart version 3.0.0 . Are you pinning Pulsar version to 2.10.2 ? In chart version 3.1.0, the default Pulsar version is 3.0.2 . |
Understood, I copied and posted the logs before updating to chart 3.1.0. After updating the issue persisted, I just didn't copy the log messages after that because they were exactly the same. |
There must be some other error messages in the k8s events etc. . My guess is that it will be necessary to set functions.rbac.limit_to_namespace to true in the values file. |
I made this PR #418 to fix the issue that the chart uses cluster level role & role bindings by default. |
You could also test with passing |
another one to test is @theoribeiro |
@lhotari
|
@lhotari Also happening after setting Here are the full logs of the broker's initialization:
|
Thanks @theoribeiro , this gives a clear picture of what happened. I won't be able to work on this until next year. |
No worries, @lhotari. Any chance I can help? |
Having clear repro steps would help so that I could follow the same steps and reproduce on GKE. Perhaps you already provided this info somewhere? |
@theoribeiro Please share your values file (or |
@theoribeiro Do you have a chance to test with latest Apache Pulsar Helm Chart release 3.2.0 ? |
@theoribeiro Do you have a chance to test with latest Apache Pulsar Helm Chart release 3.4.1 . Please reopen the ticket if the problem reproduces with 3.4.1. |
Describe the bug
I'm installing the helm on GKE with Autopilot turned on but my brokers fail starting up. If I turn off functions by setting
components.functions: false
the brokers start up correctly.This is the exception on my brokers' initialization:
Any ideas on what may be causing this?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected the helm chart to install the cluster correctly with no errors.
The text was updated successfully, but these errors were encountered: