-
Notifications
You must be signed in to change notification settings - Fork 111
Closed
Description
I ran the CSI driver with liveness probe for several days and the liveness probe memory usage turned to be 765MB which is abnormal compared to other csi sidecars.
The follow is a screenshot from htop
:
Another side affect is my CSI driver turned to be crashing a lot more after liveness probe is enabled:
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system dns-controller-64db5996cd-wvrmv 1/1 Running 0 6d7h
kube-system ebs-csi-controller-0 6/6 Running 36 5d18h
kube-system ebs-csi-node-djvrx 3/3 Running 20 5d18h
kube-system ebs-csi-node-g2c2k 3/3 Running 9 5d18h
Here is my liveness probe config:
livenessProbe:
httpGet:
path: /healthz
port: healthz
initialDelaySeconds: 10
timeoutSeconds: 3
periodSeconds: 10
failureThreshold: 5
Metadata
Metadata
Assignees
Labels
No labels