aboutsummaryrefslogtreecommitdiffstats
path: root/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
diff options
context:
space:
mode:
Diffstat (limited to 'server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md')
-rw-r--r--server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md b/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
index 1664fb22781..c55162658f1 100644
--- a/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
+++ b/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
@@ -96,8 +96,8 @@ Monitoring through this endpoint requires authentication. You can access the end
- **`X-Sonar-Passcode: xxxxx` header:** You can use `X-Sonar-passcode` during database upgrade and when SonarQube is fully operational. Define `X-Sonar-passcode` in the `sonar.properties` file using the `sonar.web.systemPasscode property`.
- **username:password and JWT token:** When SonarQube is fully operational, system admins logged in with local or delegated authentication can access the endpoint.
-####**JMX Exporter**
-You can also expose at the JMX metrics to Prometheus with the help of the Prometheus JMX exporter.
+#### **JMX Exporter**
+You can also expose the JMX metrics to Prometheus with the help of the Prometheus JMX exporter.
To use this option, set the following values in your `values.yaml` file: