vault-0 pods stay in status to "ContainerCreating"

**Describe the bug**
I try to deploy vault on my AKS cluster but the vault-0 pods keep status to "ContainerCreating" indefinitly

**To Reproduce**
Steps to reproduce the behavior:
1. Install chart with command
```
helm install vault hashicorp/vault \
--set='ui.enabled=true' \
--set='ui.serviceType=LoadBalancer'
```
2. I found those events in the log
```
default 0s Normal Scheduled pod/vault-0 Successfully assigned default/vault-0 to aks-XXX
default 0s Warning FailedAttachVolume pod/vault-0 AttachVolume.Attach failed for volume "pvc-XXX" : Retriable: true, RetryAfter: 0s, HTTPStatusCode: -1, RawError: Code="RetryableError" Message="A retryable error occurred."
default 0s Normal SuccessfulAttachVolume pod/vault-0 AttachVolume.Attach succeeded for volume "pvc-XYXYXYXY"
default 0s Normal Pulled pod/vault-agent-injector-USUUSUSU-dtdttdd Successfully pulled image "hashicorp/vault-k8s:0.10.0" in 7.171429921s
default 0s Normal Created pod/vault-agent-injector-USUUSUSU-dtdttdd Created container sidecar-injector
default 0s Normal Started pod/vault-agent-injector-USUUSUSU-dtdttdd Started container sidecar-injector
default 0s Normal EnsuredLoadBalancer service/vault-ui Ensured load balancer
default 0s Warning FailedMount pod/vault-0 Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[vault-token-fv6xs data config home]: timed out waiting for the condition
default 0s Warning FailedMount pod/vault-0 Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[vault-token-fv6xs data config home]: timed out waiting for the condition

```
I have this behaviour randomly but very often

**Expected behavior**
I just want to have a well started pod to use vault

**Environment**
* Kubernetes version:
* AKS
* v1.19.9
* vault-helm version:
* vault-0.11.0

Does anyone has an idea to resolve my problem