[GitHub] [rocketmq-operator] vongosling commented on a change in pull request #5: Add Broker Horizontal Up-scale and Broker Rolling Update when Name Service Scaling

[GitBox <gi...@apache.org>]

vongosling commented on a change in pull request #5: Add Broker Horizontal Up-scale and Broker Rolling Update when Name Service Scaling
URL: https://github.com/apache/rocketmq-operator/pull/5#discussion_r325583111
 
 

 ##########
 File path: README.md
 ##########
 @@ -287,10 +307,45 @@ $ cat default-broker-storage-broker-1-master-0-pvc-d7b76efe-384c-4f8d-9e8a-ebe20
 ...
 ```
 
+## Horizontal Scale
+
+### Name Server Cluster Scale
+If the current name service cluster scale does not fit your requirements, you can simply use RocketMQ-Operator to up-scale or down-scale your name service cluster.
+
+If you want to enlarge your name service cluster. Modify your name service CR file ```rocketmq_v1alpha1_nameservice_cr.yaml```, increase the field ```size``` to the number you want, for example, from ```size: 1``` to ```size: 2```.
+
+> Notice: if your broker image version is 4.5.0 or earlier, you need to make sure that ```allowRestart: true``` is set in the broker CR file to enable rolling restart policy. If not, configure it to true and run ```kubectl apply -f example/rocketmq_v1alpha1_broker_cr.yaml``` to apply the new config.
 
 Review comment:
   If not, configure it to false

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services