doc/cephadm: remove step to restart the mgr

a restart of the mgr does not appear to be necessary
after a `ceph config-key set ...`

Signed-off-by: Michael Fritch <mfritch@suse.com>

diff --git a/doc/cephadm/monitoring.rst b/doc/cephadm/monitoring.rst
index adacc0104dd5816f59889f96e094671b8c3a5704..e2e180c22bfcb31ef70e5290b48580f2aea01d86 100644 (file)
--- a/doc/cephadm/monitoring.rst
+++ b/doc/cephadm/monitoring.rst
@@ -119,13 +119,6 @@ A custom certificate can be configured using the following commands.
   ceph config-key set mgr/cephadm/grafana_key -i $PWD/key.pem
   ceph config-key set mgr/cephadm/grafana_crt -i $PWD/certificate.pem
 
-The ``cephadm`` manager module needs to be restarted to be able to read updates
-to these keys.
-
-.. code-block:: bash
-
-  ceph orch restart mgr
-
 If you already deployed Grafana, you need to ``reconfig`` the service for the
 configuration to be updated.
 
@@ -244,8 +237,8 @@ To set contents of files as template use the ``-i`` argument:
   When using files as input to ``config-key`` an absolute path to the file must
   be used.
 
-It is required to restart the cephadm mgr module after a configuration option
-has been set. Then the configuration file for the service needs to be recreated.
+
+Then the configuration file for the service needs to be recreated.
 This is done using `reconfig`. For more details see the following example.
 
 Example
@@ -257,9 +250,6 @@ Example
   ceph config-key set mgr/cephadm/services/prometheus/prometheus.yml \
     -i $PWD/prometheus.yml.j2
 
-  # restart cephadm mgr module
-  ceph orch restart mgr
-
   # reconfig the prometheus service
   ceph orch reconfig prometheus