You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When altering the zeebe.partitionCount, you always have to adjust the optimize.partitionCount as well.
Describe the enhancement/feature:
Instead of having zeebe.partitionCount, zeebe.replicationFactor and zeebe.clusterSize, offer these values globally so that every component that relies on these numbers can use them and is in sync.
Desired outcome and acceptance tests:
There is no more than one (globally accessible) section in the values.yaml that describe the cluster sizing.
The text was updated successfully, but these errors were encountered:
Describe the use case:
When altering the
zeebe.partitionCount
, you always have to adjust theoptimize.partitionCount
as well.Describe the enhancement/feature:
Instead of having
zeebe.partitionCount
,zeebe.replicationFactor
andzeebe.clusterSize
, offer these values globally so that every component that relies on these numbers can use them and is in sync.Desired outcome and acceptance tests:
There is no more than one (globally accessible) section in the
values.yaml
that describe the cluster sizing.The text was updated successfully, but these errors were encountered: