Bug on Kubernetes Cluster Agent new version 23.6.0

[Everton.Arakaki]

Before 23.6.0, the agent was respecting the parameter:

    instrumentationConfig:

        numberOfTaskWorkers: 2

After 23.6.0, this config is not been respected and many instrumentation happens leading to high cpu usage. I tried all parameters but it looks a bug to me, it was working before. I'm using this config. All my java services have readiness and liveness probes.

    clusterAgent:

        containerProperties:

            containerBatchSize: 1

            containerParallelRequestLimit: 1

            podBatchSize: 1

    instrumentationConfig:

        numberOfTaskWorkers: 1

        podBatchSize: 2

please help

[Ryan.Paredez]

Hi @Everton.Arakaki,

Thanks for sharing this with the Community. For an issue that you believe is a bug, it's best to report it to Support as well. It's helpful to share in the community so others may know it's an issue.

Support will be able to get it reported to engineering in a different avenue.

How do I submit a Support ticket? An FAQ 

[Virendra.Singh]

@Ryan.Paredez Is there any update on this? I am also struggling with the same issue. Changing it to a higher number (e.g., 5) or a lower number (e.g., 1) doesn't work. It's taking a default value of 2.

[Ryan.Paredez]

Hi @Everton.Arakaki,

Did you ever reach out to Support and get a reply?