As discussed with aparedes@redhat.com mfentanes abakos@redhat.com rhn-support-alazarot KrisVerlaenen, please tag as necessary:

To sync with Business Central (BC) and deploy services when the user deploys them through UI, KIE server initiates a connection to Controller, which is a component of BC.

In an HA deployment, Controller instances are not synchronized. And load-balancing means that a KIE server can be connected to any of the cluster instances randomly. If a user uses the UI to deploy a service on the KIE server, but the user is connected to another cluster instance, the service is never deployed. Other sync issues are also possible.

csherrar : the agreed workaround, for now, was to document that one should not connect KIE servers to BC HA on-prem. I will create a separate JIRA for documenting this and assign to you.

[NOTE ENG]
This requires in case of using VFS to sync / share the state.

<property name="org.uberfire.nio.git.dir" value="/opt/kie/niogit"/>

Kie Server will notify the controller about needs to be refreshed and it will pick it up from there.

In case of openshift strategy we should be fine.

[ENG NOTE]
Added a property to disable notification from kie server to controller. By default is true

org.kie.server.update.notifications.rest.enabled=true