Open TheKangaroo opened 6 years ago
Hi @TheKangaroo - Is it still an issue? Did you managed to deploy jBPM in Kubernetes cluster?
We want to deploy this in Kubernetes and want to have control over the size of each component of jBPM. For example we would like to assign more pods (or scaling policy) to process executors.
Hi @ndass-sapient, we had this running as a test setup, but just a single instance and no individual scaling of the components, in other words: a very basic setup. I think there is some work to do on the app side. Since nobody ever responded to this issue I don't think this is a priority for the developers, unfortunately.
Hi @TheKangaroo, did you fix it ? Can you share , I also have this problem
@bongbk unfortunately no, we never came back to try to fix this. But as I said early, I don't think this is something you can fix in kubernetes deployment. jbpm just does not support to run with multiple instances at once.
My feeling is that if you want "JBPM in Kubernetes", then you need to look at Kogito, the kubernetes-ready solution for workflows. It is still BPMN but with Kubernetes-friendly (as long as Kubernetes can be friendly to your team, that is ... but this is another story!
Hey guys, I just wanted to deploy jbpm to my kubernetes cluster, but saw in your doc's at docker hub that
Does this apply to kubernetes as well? Which problems occur on cloud environments? I started the app with replicas: 1, but it failed to log in, as soon as I increased the replica count.