Don't reset the payload node when it goes leaderless if:
export CL_AMF_PAYLOAD_RESET_DISABLE=1
This would ensure that the payloads continue to run without terminating the services even
when the cluster becomes leaderless.
When a master joins the cluster, the payload registration thread, re-registers back with master.
The master then continues with payload instantiation as before. But it would end up being a soft instantiation as instantiated components wouldn't be re-instantiated by payloads and csi assignments wouldn't be reassigned because the client side csi cache for the components on the payload would ensure that the component won't get duplicate csi assignments for the same CSI.
In effect, it would end up being a cluster start with same role assignments triggered from master as before.
When any application is killed in the payload in the absence of the master, then the component is only cleaned up locally. It would end up getting instantiated when the master tries to instantiate the payload after it re-registers with master on seeing a cluster leader.