Scheduling reporting pods

By default, an admin is not required to do anything for Engineering Lifecycle Management instance creation to succeed. However, in certain cases it is necessary to make adjustments to accommodate clusters with small number of nodes. When a cluster has only three worker nodes, then all the three nodes are quickly occupied by the application or common pods. This causes reporting pods to stay in the "Pending" state due to lack of nodes that are available, which satisfy affinity rules. To solve this problem, before creating an Engineering Lifecycle Management instance, select a node where reporting pods can be scheduled.

1. In the Red Hat® OpenShift® Container Platform web console click Compute > > Nodes.
2. Click More actions on the required node.
3. From the context menu, click Edit Labels.
   Edit Labels window appears where you are able to add or remove labels.
4. Add the label elm.ibm.com.type=reporting and click Save.