Join this online user group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
The support for tolerations on integrations has been added previously which allows greater control of where and how your integrations are scheduled across your Red Hat OpenShift or Kubernetes worker nodes. As of App Connect Operator `v12.6.0`, operand version `13.0.1.1-r1`, we now have this support for the App Connect Dashboard containers. Note that unlike the Integration Runtime container, the App Connect Dashboard is a "FREE" container so toleration support is more of a case of scheduling and organization rather than licensing considerations.
Scheduling through tolerations can be achieved using the new custom resource (CR) fields `tolerations` and `nodeSelector` to specify where the pod can run when using tainted nodes:
spec: pod: nodeSelector: workloadType: ace tolerations: - effect: NoSchedule key: workloadType operator: Equal value: ace
spec:
pod:
nodeSelector:
workloadType: ace
tolerations:
- effect: NoSchedule
key: workloadType
operator: Equal
value: ace
A worked example can be seen on the integration scheduling post.
For further information on how these can be used refer to Taints and Tolerations.
Copy