Update docs to main

Author: Arkmq Bot

Diff for: content/en/docs/help/building.md

@@ -19,7 +19,7 @@ toc: true
 
 ### Go
 
-Download the Go version v1.21.11 from the [download page](https://go.dev/dl/) and install it following the [installation instructions](https://go.dev/doc/install).
+Download the Go version v1.22.7 from the [download page](https://go.dev/dl/) and install it following the [installation instructions](https://go.dev/doc/install).
 
 ### Operator SDK
 

Diff for: content/en/docs/help/operator.md

@@ -628,7 +628,7 @@ spec:
 
 ###  Tolerations
 
-It is possible to configure tolerations on tge deployed broker image . An example of a toleration would be something like:
+It is possible to configure tolerations on the deployed broker image . An example of a toleration would be something like:
 
 ```yaml
 apiVersion: broker.amq.io/v1beta1
@@ -1065,6 +1065,10 @@ The operator supports a level of indirection when resolving versions, there are
 The operator will validate the a CR specifies both image and initImage or a Version. It will also validate that a speficied version matches the internal list of supported versions.
 The CR Status sub resource will contain feedback via the Valid Condition if validation fails.
 
+## Disabling reconcile with the `arkmq.org/block-reconcile` annotation
+
+In cases where a rollout of the stateful set is necessitated via a new feature or bug fix but not immediately desirable, potentially because of the necessary broker restart, it is possible to block the reconcile of a CR. Applying the `arkmq.org/block-reconcile` boolean annotation to a CR will indicate that the operator should not reconcile the CR. The CR status will reflect the blocked state via an additional `ReconcileBlocked` Condition. Once the annotation is removed or set to false on the CR, reconcile will resume.
+
 
 ## Enable broker's metrics plugin
 
@@ -1223,11 +1227,25 @@ The operator uses jolokia endpoints to get broker status and also create queue/a
 
 To gain access to jolokia the operator need to have proper credentials (username/password).
 
-By default the operator gets the username and password from the broker container's environment variables AMQ_USER and AMQ_PASSWORD. The operator exposes the environment variables with the values defined in the broker CR's **spec.adminUser** and **spec.adminPassword** fields.
+By default, the operator retrieves the username and password from the broker container's environment variables `AMQ_USER` and `AMQ_PASSWORD`. These environment variables are populated with values from the secret **[broker CR name]-credentials-secret**, using the `AMQ_USER` and `AMQ_PASSWORD` keys.
+
+If you specify adminUser and adminPassword in the broker CR, these values will be written to the auto-generated secret **[broker CR name]-credentials-secret**, using the `AMQ_USER` and `AMQ_PASSWORD` keys.
 
-If you configure **adminUser** and **adminPassword** in the broker CR the values will be populated into the environment variables AMQ_USER and AMQ_PASSWORD respectively.
+Alternatively, you can provide your own secret named **[broker CR name]-credentials-secret**, which must contain four entries: `AMQ_USER` / `AMQ_PASSWORD` for administrative access, and `AMQ_CLUSTER_USER` / `AMQ_CLUSTER_PASSWORD` for intra-cluster communication.
 
-Alternatively you can provide a secret called **[broker cr name]-credential-secret** within which contains 2 entries whose keys are `AMQ_USER` and `AMQ_PASSWORD` respectively, with corresponding values for each.
+```yaml
+apiVersion: v1
+metadata:
+  name: amq-credentials-secret
+  namespace: default
+kind: Secret
+type: Opaque
+stringData:
+  AMQ_USER: admin
+  AMQ_PASSWORD: adminPassword
+  AMQ_CLUSTER_USER: cluster
+  AMQ_CLUSTER_PASSWORD: clusterPassword
+```
 
 However when you use security CRs, jass login module configs, or init container to configure security login modules,
 The above adminUser and adminPassword may be overridden and jolokia client in the operator won't be able to get the correct credentials to connect to the broker. In that case the user should provide a secret called **[broker cr name]-jolokia-secret**, in which you put 2 entries for username and password for jolokia credential to use. The 2 entries should have keys named **jolokiaUser** and **jolokiaPassword** respectively, the value for **jolokiaUser** is the user name and the value for **jolokiaPassword** is the password.