Jared Tan

> ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator@sha256:2bab7a2dd5f7aee9dabdf85cd040d3bcd3fc29a4175260bd385d8bd5bc75963a thx, It works!

Similarly, I'll finish this after https://github.com/open-telemetry/opentelemetry-helm-charts/pull/968 merged

> I'm adding a bump for this functionality. It looks like #968 was merged. Can we add this additional functionality as I too am prevented from deploying without some custom...

> @JaredTan95 based on #912 it seems like you are testing this out. Would you mind sharing any findings about the setting (memory and CPU usage patterns before/after?) > >...

> I'd think we should keep useGOMEMLIMIT: true for a couple of versions, then deprecate memory_ballast extension I agree! 👏

> @JaredTan95 can you please share more details about memory ballast's compatibility issues with our arm architecture? It be nice to post them in [open-telemetry/opentelemetry-collector#8343](https://github.com/open-telemetry/opentelemetry-collector/issues/8343) as well The compatibility problem...

I think it should be solved by https://github.com/open-telemetry/opentelemetry-demo/pull/244 becauese the opentelemetry-operator will inject the `java` agent sidecar/initcontainer and override the `JAVA_TOOL_OPTIONS` value. ```bash annotations: instrumentation.opentelemetry.io/inject-java: otel-agent-xxxxx ```

@aacevedoosorio thx, pls bump up the chart version by following [CONTRIBUTING docs](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/CONTRIBUTING.md)

have you created your `instrumentation` CR? pls following https://github.com/open-telemetry/opentelemetry-operator?tab=readme-ov-file#opentelemetry-auto-instrumentation-injection

@shishir84 could you paste the logs of `opentelemetry-operator-56b9cc5565-klzp2`?