CSI Driver down time is impacting Application Pods

[Priyadarsini_M]

Hi Dynatrace Team,

We are using Cloud Native Full stack where csi driver is getting used in our kubernetes cluster.
Today in one of the cluster for completely different issue all the dynatrace and application pods are down and after sometime that issue has been solved but still the application pods aren’t up. 
When trying to redeploy the application pods this following error occured-

Mount Volume.SetUp failed for volume "oneagent-bin" : kubernetes.io/csi:mounter.SetUpAt failed to get CSI client: driver name csi.oneagent.dynatrace.com not found in the list of registered CSI drivers

When checked the Dynatrace pods, csi-driver and oneagent pods were still in evicted state.

After deleting these evicted pods manually, both csi-driver and oneagent pods were started properly.

Only after Dynatrace pods were up, application pods also started successfully.

Can you please help and suggest a way to avoid the application impact due to Dynatrace pods state.

[IzabelaRokita · Accepted solution]

Hey @Priyadarsini_M !
Sorry for the delay. Our Community gets lots of activity every day, and unfortunately, sometimes, some posts don't get as much attention as they deserve. Did you find an answer to your question, or would you like me to seek further assistance for you? 

[Priyadarsini_M]

Hi @IzabelaRokita ,

Thanks for the response, I got my answers.

[gabriel_gomez]

Puedes compartir la solución, tengo el mismo problema 

[gabriel_gomez]

Can you share the solution? I had to uninstall it so it wouldn't affect production. The pods weren't uploading, or sometimes it took almost 30 minutes to upload.

[g_kat]

Hi,

@Priyadarsini_M could you share the solution you got about the ways to avoid impact to application pods due to Dynatrace components not operational? We have a case where we can't pull the Operator image from RedHat registry and the CSI drivers basically stop application pods from initializing.

Thanks,

George