AntiAffinity for LokiStack components to not run everything on the same OpenShift Container Platform 4 - Node

Proposed title of this feature request
AntiAffinity for LokiStack components to not run everything on the same OpenShift Container Platform 4 - Node

What is the nature and description of the request?
In Cloud Native environments it's common practice to define Affinity or AntiAffinity rules for application to improve resilience or performance.

LokiStack should thus have some default AntiAffinity rules applied to improve overall resilience of the service and prevent running the complete stack on one or just two OpenShift Container Platform 4 - Node that could create a problematic scenario in case of such a OpenShift Container Platform 4 - Node failure.

Why does the customer need this? (List the business requirements)
Cloud Native application in general should have Affinity or AntiAffinity rules defined to improve performacne and/or resilience. In case of LokiStack, AntiAffinity is desired to spread the workload across multiple OpenShift Container Platform 4 - Nodes and therefore improve the overall resilience.

List any affected packages or components.
LokiStack