Get rid of separate broker and brokerSts configuration keys from values.yaml
lhotari opened this issue · 0 comments
lhotari commented
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.