From d526be896169435fb57439956923fbd5eed47b02 Mon Sep 17 00:00:00 2001 From: Redouane Kachach Date: Wed, 5 Oct 2022 16:36:15 +0200 Subject: [PATCH] doc/cephadm: fixing grafana cet/key generation documentation Fixes: https://tracker.ceph.com/issues/57769 Signed-off-by: Redouane Kachach --- doc/cephadm/services/monitoring.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/cephadm/services/monitoring.rst b/doc/cephadm/services/monitoring.rst index 0f67d3f0044e..5a0bdb385ed9 100644 --- a/doc/cephadm/services/monitoring.rst +++ b/doc/cephadm/services/monitoring.rst @@ -408,14 +408,17 @@ Configuring SSL/TLS for Grafana ``cephadm`` deploys Grafana using the certificate defined in the ceph key/value store. If no certificate is specified, ``cephadm`` generates a -self-signed certificate during the deployment of the Grafana service. +self-signed certificate during the deployment of the Grafana service. Each +certificate is specific for the host it was generated on. A custom certificate can be configured using the following commands: .. prompt:: bash # - ceph config-key set mgr/cephadm/grafana_key -i $PWD/key.pem - ceph config-key set mgr/cephadm/grafana_crt -i $PWD/certificate.pem + ceph config-key set mgr/cephadm/{hostname}/grafana_key -i $PWD/key.pem + ceph config-key set mgr/cephadm/{hostname}/grafana_crt -i $PWD/certificate.pem + +Where `hostname` is the hostname for the host where grafana service is deployed. If you have already deployed Grafana, run ``reconfig`` on the service to update its configuration: -- 2.47.3