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

Get rid of separate broker and brokerSts configuration keys from values.yaml #200

Open
lhotari opened this issue Apr 27, 2022 · 0 comments
Open

Get rid of separate broker and brokerSts configuration keys from values.yaml #200

lhotari opened this issue Apr 27, 2022 · 0 comments

Comments

@lhotari
Copy link
Contributor

lhotari commented Apr 27, 2022

Currently, configuring brokers in the values.yaml is confusing, since an implementation detail impacts the configuration keys for broker configuration.

When a "stateful set" is used, the configuration key is brokerSts and when a deployment is used, the configuration key is broker. This isn't very intuitive.

Consider resolving this problem in the 3.0 version of the chart.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lhotari