We have seen issues when running the stack locally via Docker as it could not have enough memory allocated. To run all the granular microservices locally takes A LOT of RAM. These are the Docker config recommendations for balanced: Broadleaf Dev Central . Please note that the higher end memory allocation of 25 GB shown in those docs is still likely not enough to run all the granular services at the same time.
We want you to be aware of the large resource requirements that are needed when you move to Kubernetes as well. Please refer the documentation from here around configuring and using Kubernetes Camel Cluster Service (if you choose to use this). There may be significant amount of resources needed for the K8 Master Nodes/Control Plane as well.
If you have a rather large topology (e.g. deploying multiple replicas of a full granular deployment) and you are seeing substantial CPU usage on the Kubernetes API Master Nodes/Control Plane, you may find it beneficial to tune the Apache Camel Kubernetes Config Options, such as the renew-deadline, jitter-factor, and lease-duration.
Note: another option/recommendation would be to use Zookeeper instead (which is also described in the same documentation page).