Just setup two camunda nodes that point to the same database - they should be identical in terms of deployments and settings.
Add a load balancer in front of the nodes - if you’re using cockpit you’ll need to use sticky sessions.
Depending on how you actually deploy processes - via REST or through the use of a WAR file certain changes will need to be made to the engine settings.
I am trying to work something out on the same lines and here is the issue I faced. I am deploying the process as an xml file placed inside the resources folder of my spring boot app. Now once Pods are alive and lets say two pods received the request, Cockpit starts showing 2 versions of the same process and it gets really confusing.
Am i missing something like Kubernetes related property or something?
Do you mean two running processes or two versions of the process definition? If the latter, both pods are probably individually deploying the process BPMN file on startup.