Skip to content

Commit

Permalink
[CORE-106517] Fix outdated config in the sample (#83)
Browse files Browse the repository at this point in the history
  • Loading branch information
aguzovatii authored Jun 4, 2024
1 parent 7f2632a commit b37a977
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions config/samples/banzaicloud_v1beta1_kafkacluster.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -55,13 +55,13 @@ spec:
# alerts with 'rollingupgrade'
# failureThreshold: 1

# concurrentBrokerRestartsAllowed controls how many brokers can be restarted in parallel during a rolling upgrade. If
# concurrentBrokerRestartCountPerRack controls how many brokers can be restarted in parallel during a rolling upgrade. If
# it is set to a value greater than 1, the operator will restart up to that amount of brokers in parallel, if the
# brokers are within the same AZ (as specified by "broker.rack" in broker read-only configs). Since using Kafka broker
# racks spreads out the replicas, we know that restarting multiple brokers in the same rack will not cause more than
# 1/Nth of the replicas of a topic-partition to be unavailable at the same time, where N is the number of racks used.
# This is a safe way to speed up the rolling upgrade.
# concurrentBrokerRestartsAllowed: 1
# concurrentBrokerRestartCountPerRack: 1

# brokerConfigGroups specifies multiple broker configs with unique name
brokerConfigGroups:
Expand Down

0 comments on commit b37a977

Please sign in to comment.