Proposed title of this feature request
PodDisruptionBudget for LokiStack to keep the stack up and running and under control during OpenShift Container Platform 4 - upgrades

What is the nature and description of the request?
In OpenShift Container Platform 4, updates are applied based on MachineConfigPool level, requiring customers to apply PodDisruptionBudget to prevent undesired disruption when OpenShift Container Platform 4 - Nodes are being updated/rebooted.

LokiStack is missing PodDisruptionBudget configuration, which could trigger all OpenShift Container Platform 4 - Nodes, hosting such components to be updated at the same time and therefore restart the entire service at the same time, which may introcued undesired service disruption.

To avoid that, a PodDisruptionBudget should be defined that controls the availability of the LokiStack and makes sure that during controlled OpenShift Container Platform 4 - Node maintenance only service degration is happening because replicas are restarting but no service disruption because all services are offline at once.

Why does the customer need this? (List the business requirements)
OpenShift Container Platform 4 - updates are designed in a way that disruption can happen at any time. Hence all services are required to maintain a proper PodDisruptionBudget to prevent complete failure of a service.

LokiStack should comply with those requirements to prevent undesired service disruption and to show-case how to manage and maintain Cloud Native application on OpenShift Container Platform 4.

List any affected packages or components.
LokiStack