Engineering Lifecycle Management pod and node affinity rules

Edit online

The pods that are deployed by Engineering Lifecycle Management instance operator are preconfigured with a set of affinity rules. These pods help in achieving high availability and avoid co-location of application pods with monitoring and reporting ones.

Engineering Lifecycle Management affinity rules

Engineering Lifecycle Management pods can be classified into three categories.

Applications (Engineering Requirements Management DOORS® Next, Engineering Workflow Management, Engineering Test Management, Engineering Insights)
Common (Jazz® Team Server, Jazz Authorization Server, Global Configuration Management)
Reporting (LQE, Data Collection Component), Report Builder

Affinity rules set for Engineering Lifecycle Management pods ensure that the reporting pods are never co-located with common or application pods. All pods are as distributed across all available nodes as possible. If a node contains a label elm.ibm.com.type=reporting, then this node is reserved for any reporting pod (LQE or Data Collection Component).