provisioner container in dynatrace-oneagent-csi-driver restarts several times when pod scheduled

[Tomy8s]

Describe the bug

provisioner container in the dynatrace-oneagent-csi-driver pods is restarted several times immediately after the pod is spun up.

To Reproduce

• Release operator to a cluster
• When stable, scale out cluster

Expected behavior

All containers in the dynatrace-oneagent-csi-driver should report as healthy after reporting as started up

Screenshots

% kubectl get pod -l internal.oneagent.dynatrace.com/app=csi-driver                                     
NAME                                  READY   STATUS    RESTARTS       AGE
dynatrace-oneagent-csi-driver-2659v   4/4     Running   0              37h
dynatrace-oneagent-csi-driver-2b9gt   4/4     Running   1 (37h ago)    37h
dynatrace-oneagent-csi-driver-2bf7s   4/4     Running   1 (37h ago)    37h
dynatrace-oneagent-csi-driver-2c4lc   4/4     Running   1 (139m ago)   139m
dynatrace-oneagent-csi-driver-2drmj   4/4     Running   3 (159m ago)   160m
dynatrace-oneagent-csi-driver-2f4jw   4/4     Running   2 (36h ago)    36h
dynatrace-oneagent-csi-driver-2frfx   4/4     Running   2 (36h ago)    36h
dynatrace-oneagent-csi-driver-2qk7r   4/4     Running   4 (36h ago)    36h
dynatrace-oneagent-csi-driver-2sbtm   4/4     Running   1 (36h ago)    36h
dynatrace-oneagent-csi-driver-2wdq7   4/4     Running   1 (37h ago)    37h
dynatrace-oneagent-csi-driver-4mr78   4/4     Running   0              36h
dynatrace-oneagent-csi-driver-4p8wd   4/4     Running   1 (179m ago)   3h
dynatrace-oneagent-csi-driver-5d449   4/4     Running   3 (36h ago)    37h
dynatrace-oneagent-csi-driver-5qxqh   4/4     Running   1 (37h ago)    37h
dynatrace-oneagent-csi-driver-5s895   4/4     Running   1              35h
dynatrace-oneagent-csi-driver-5zdlw   4/4     Running   1 (36h ago)    36h
...

Additional context

• There is a startupProbe configured for the server container in the same pod in csi/daemonset.yaml.
• There is no startupProbe configured for the provisioner container.
• These containers both use the same dynatrace-operator.image image.

Would adding the same startupProbe to the provisioner container fix this issue?

[github-actions]

Thank you for opening a Dynatrace Operator Issue. We've identified and tagged the issue as a "Support request".

Dynatrace responds to requests like these via Dynatrace ONE support rather than Github. This helps our team respond as quickly as possible using the support team's tools and procedures.

Thanks for your help!