CPU Throttling on CSI Driver Pods

[ntanaka]

Question

We are experiencing frequent CPU throttling on CSI driver Pods of Dynatrace Operator.
The CPU throttling rate is 600-700%.

Has anyone experienced similar issues in their environment?

If yes, what actions did you take to resolve them? How much should we increase the CPU limits?

We have already increased the CPU limits compared to the defaults, but throttling still occurs.
In your experience, how much did you increase the CPU limits to mitigate this?

Current Situation

CPU throttling is happening on CSI driver Pods, but there is no immediate impact on workloads.
However, in the past, we had a CrashLoopBackOff issue with the CSI driver, which prevented business-critical Pods from starting. So, we concerned about potential CPU shortages.

Environment

• OpenShift 4.14
• Kubernetes 1.27
• Dynatrace Operator v1.4.1

Resource Configuration

name: server
resources:
  limits:
    cpu: "1"       # default: 50m
    memory: 600Mi  # default: 100Mi
  requests:
    cpu: 300m      # default: 50m
    memory: 600Mi  # default: 100Mi

name: provisioner
resources:
  requests:
    cpu: 300m
    memory: 100Mi

name: registrar
resources:
  limits:
    cpu: 20m
    memory: 30Mi
  requests:
    cpu: 20m
    memory: 30Mi

name: liveness-probe
resources:
  limits:
    cpu: 200m      # default: 20m
    memory: 300Mi  # default: 30Mi
  requests:
    cpu: 20m
    memory: 30Mi

[Michal_Gebacki · Accepted solution]

Hello, @ntanaka!

Is this Dynatrace Documentation page helpful in any way? Please let us know, any feedback is greatly appreciated!

-> Set resource limits for Dynatrace Operator components

[Julius_Loman]

Hello @ntanaka 

I highly recommend upgrading your Dynatrace Operator first to 1.7.1 or 1.7.2 at least as there have been some issues resolved which might cause symptoms you see, especially the CrashLoopBackOff.