I’m using Camunda 8, self-hosted on AWS and deploying it via Helm charts in an EKS environment. Our current setup involves deploying BPMNs using the deprecated spring-zeebe library, as we’re waiting for the updated library release in Camunda 8.7.
The specific issue I’m encountering relates to the deployment of BPMN files when the server restarts.
Here’s the setup:
- I’m deploying BPMN files using the
@Deployment(resources = "classpath*:/bpmn/**/*.bpmn")annotation. - When I restart the server locally, without altering any BPMN file, it does not trigger a redeployment (as expected).
- However, when I restart the server on EKS, a new BPMN deployment is triggered each time, even when there are no BPMN file changes.
Does anyone have experience with this behavior on AWS EKS or know why the server restart on EKS might be triggering new deployments? Any insights on how to avoid these redeployments would be greatly appreciated.
Thanks in advance!