Bug 1889647 - Document that user should add more worker nodes when PodDisruptionBudgetAtLimit alert is triggered
Summary: Document that user should add more worker nodes when PodDisruptionBudgetAtLim...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat
Component: documentation
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Anjana Suparna Sriram
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 09:57 UTC by Filip Balák
Modified: 2020-10-20 10:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1817876 unspecified CLOSED PodDisruptionBudgetAtLimit alert for all OSDs after installation 2020-10-20 09:57:14 UTC

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.


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