Activiti: [k8s configurations] on services check memory and cpu limits

[salaboy]

Are they set?
Are we stopping the services to start faster?

[almerico]

@salaboy can you please add more details

[salaboy]

We need to review this values:
https://github.com/Activiti/example-runtime-bundle/blob/master/charts/example-runtime-bundle/values.yaml#L58

I can see that we are not setting CPU limits.. but CPU 400 means that it will allocate 0.4 cpu resources by default to this container, which is why the spring boot app takes forever to start.

We also need to change the liveness probe to not use the actuator path.. the liveness check should check that the JVM is active, and it should never kill the container unless the JVM crash.. today we are killing the container even if we are still retrying to connect to rabbitMQ.

https://github.com/Activiti/example-runtime-bundle/blob/master/charts/example-runtime-bundle/values.yaml#L64

hopefully that makes more sense.

[almerico]

@salaboy understand taking a look

[almerico]

@salaboy I played some times with different settings for services finally I changed memory and cpu settings for rabbit this was the main issue since all waited for it and also runtime bundle so now everything is started in full-examples without restarts.Working on probes now.

[salaboy]

wow!!!!! great news!! @ryandawsonuk @erdemedeiros @miguelruizdev ^^^^^

[miguelruizdev]

That's amazing!!!
Thanks @almerico

[salaboy]

let's close this one then