High Memory Consumption of liveness-probe Container in CSI Driver Pod

ntanaka — Fri, 28 Nov 2025 04:28:45 GMT

Hi everyone,

Question:

We are experiencing high memory consumption of the liveness-probe container in the CSI driver Pod when using Dynatrace Operator.

Has anyone experienced the similar issues?

Or, does anyone have insights or best practices for addressing high memory usage by the liveness-probe?

I noticed that Dynatrace Operator v1.7.0 introduced Helm switches for the livenessProbe parameter:
https://docs.dynatrace.com/docs/shortlink/release-notes-dto-fix-1-7-0#new-features-and-enhancements

Would tuning the livenessProbe parameters help reduce resource consumption?

Background:
We previously encountered a CrashLoopBackOff issue with the CSI driver caused by liveness-probe timeouts. Despite tuning various parameters based on guidance from the support team and the Community article, the issue persisted.

Eventually, increasing the memory limit for liveness-probe from the default 30 MB to 600 MB resolved the CrashLoopBackOff.

In a test environment, we intentionally set the memory limit to 6 MB, which reproduced the timeout issue. This suggests that memory exhaustion in liveness-probe leads to timeouts.

However, the root cause of the high memory consumption remains unclear. We are investigating ways to reduce memory usage to avoid CrashLoopBackOff.

Environment:

Dynatrace Operator v1.4.1
OpenShift 4.14
Kubernetes 1.27

Current livenessProbe settings:

livenessProbe: failureThreshold: 5 #default 3 httpGet: path: /healthz port: healthz scheme: HTTP initialDelaySeconds: 15 #default 5 periodSeconds: 15 #default 5 successThreshold: 1 timeoutSeconds: 10 #default 1 name: server ports: - containerPort: 9808 name: healthz protocol: TCP - containerPort: 8080 name: metrics protocol: TCP resources: limits: cpu: "1" #default 20m memory: 600Mi #default 30Mi requests: cpu: 300m #default 20m memory: 600Mi #default 30Mi

Re: High Memory Consumption of liveness-probe Container in CSI Driver Pod

Michal_Gebacki — Tue, 16 Dec 2025 16:15:07 GMT

Hi, @ntanaka!

Take a look please at these Dynatrace Documentation pages and let us know whether is it helping to address issues you've described above.

-> Storage requirements

-> Configure node image pull

Thank you in advance!

Re: High Memory Consumption of liveness-probe Container in CSI Driver Pod

ntanaka — Fri, 26 Dec 2025 05:25:02 GMT

Hi @Michal_Gebacki ,

Thank you for your response, and sorry for the delay.

Could you please explain your idea in more detail?
I have reviewed the documentation, but I’m still not sure I understand what you mean.

Are you suggesting that we should configure the node image pull?

topic Re: High Memory Consumption of liveness-probe Container in CSI Driver Pod in Container platforms

High Memory Consumption of liveness-probe Container in CSI Driver Pod

Re: High Memory Consumption of liveness-probe Container in CSI Driver Pod

Re: High Memory Consumption of liveness-probe Container in CSI Driver Pod