Bug 1731311 - [DOCS] Notify no restart for configuring the cluster monitoring stack
Summary: [DOCS] Notify no restart for configuring the cluster monitoring stack
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.1.z
Assignee: Maxim Svistunov
QA Contact: Junqi Zhao
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-19 04:23 UTC by Daein Park
Modified: 2019-09-03 11:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-03 11:04:44 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Daein Park 2019-07-19 04:23:11 UTC
Document URL: 

* Configuring the monitoring stack 
  [https://docs.openshift.com/container-platform/4.1/monitoring/cluster-monitoring/configuring-the-monitoring-stack.html]

Section Number and Name: 

* Configuring the cluster monitoring stack
  [https://docs.openshift.com/container-platform/4.1/monitoring/cluster-monitoring/configuring-the-monitoring-stack.html#configuring-the-cluster-monitoring-stack_configuring-monitoring]

Describe the issue: 

Automatically restarted related pods(prometheus, alertmanager) after "cluster-monitoring-config" configmap is changed for configuration monitoring stack.
But this behavior does not be mentioned on the documentation.

When user delete or restart the pod immediately after modifying configmap, then useless restart can happen again by timing.
It can look like unknown restart/issue to users.

Suggestions for improvement: 

Add information such like, "If you change the config, then the related pods will start again for changes, so you need not to restart them manually." for suppressing misunderstanding.

Additional information: 

This issue is also valid on v3.11 either.


Note You need to log in before you can comment on or make changes to this bug.