-
Notifications
You must be signed in to change notification settings - Fork 44
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
feat: pulsar support nodeport #358
Conversation
description: Pulsar zookeeper. | ||
serviceKind: pulsar | ||
serviceVersion: {{ default .Chart.AppVersion .Values.clusterVersionOverride }} | ||
updateStrategy: BestEffortParallel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Serial would be better
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for components without kb role detection logic, RSM currently has bugs under the SerialUpdateStrategy strategy(issue: apecloud/kubeblocks#6785). so try the BestEffortParallel strategy to ensure normal function.
/cherry-pick release-0.8 |
🤖 says: cherry pick action finished successfully 🎉! |
(cherry picked from commit cdf8a2b)
Pulsar Broker & Proxy component support NodePort service with KB0.8 Component api.
Because the KB component api does not support version management so far, this PR uses Component api for version 3.0.2, while 2.11.2 still uses the ClusterDefinition api.
users can enable the nodeport function by setting enableNodePort=true in the pulsar-cluster helm values.