Bug 1889647

Summary:	Document that user should add more worker nodes when PodDisruptionBudgetAtLimit alert is triggered
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Filip Balák <fbalak>
Component:	documentation	Assignee:	Anjana Suparna Sriram <asriram>
Status:	NEW ---	QA Contact:	Elad <ebenahar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	agantony
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Filip Balák 2020-10-20 09:57:15 UTC

Describe the issue:
In case of PodDisruptionBudgetAtLimit alert being triggered right after OCS installation, user might not know what to do to get rid of the alert because in alert message is not enough information.

There should be a note that user usually should add more worker nodes when PodDisruptionBudgetAtLimit alert is triggered.