Mathieu Cesbron

I agree. The 'conditions' is what I have seen on other operators. So: ``` status: conditions: - lastTransitionTime: "2019-10-22T16:29:24Z" status: "True" type: ClusterScheduled - lastTransitionTime: "2019-10-22T16:29:24Z" status: "True" type: ClusterInitialized...

Thanks for the comment. Yes, I agree we should only trigger the conversion for v1beta1 version and not for v1beta2 because it’s gonna convert nothing. That’s why I removed it...

The operator is made with `operator-sdk` and there is an endpoint to access the metrics. If you feel like it you can make the PR or I will do it...

`Kondense` sidecar logs the container stats continuously and patch done, it should looks something like that: ``` {"level":"info","container":"kondense","memory_limit":50000000,"memory_time to decrease":9,"memory_total":0,"integral":0,"cpu_limit":80,"cpu_average":62, "time":"2024-08-06T01:27:38Z","message":"updated stats"} ``` Can I get more information to reproduce...

Hello, thanks for the question. I still have to check, I will update when I am sure of the answer.

It looks like it works with the JVM, here is the test I made: 1. Build a dummy java container with a minimum memory limit of 80m ```dockerfile FROM openjdk:17-jdk-alpine...

I see that we are calling the real exchanges APIs during testing, that makes the tests flaky. Is it intended ?

Same issue, is there a workaround until @sjayach MR is merged and a new version is released ?