Kubernetes AWS EBS超时等待卷状态(Kubernetes AWS EBS Timeout waiting for volume state)

 如果我创建此pod： 
 
apiVersion: v1
kind: Pod
metadata:
name: dsm-manager
spec:
containers:
- name: dsm-manager
image: ******
imagePullPolicy: Always
command:
- /sbin/init
volumeMounts:
- mountPath: /srv/project/DSMManager/snapshots
name: dsm-snapshot-storage
volumes:
- name: dsm-snapshot-storage
awsElasticBlockStore:
volumeID: aws://us-west-2b/vol-43e44482
fsType: ext4
imagePullSecrets:
- name: dockerregistrykey
 
 它总是有效，但如果我删除它并重新创建它就会陷入状态'CreatingContainer'。 看事件产量： 
 - 无法为pod“dsm-manager_default”装入卷：超时等待卷状态 
 - 错误同步窗格，跳过：超时等待卷状态 
 
 如果我删除pod并重新创建它，无论我做什么都会发生同样的事情。 但是，如果我将卷附加到某个实例，然后通过aws cli将其分离，则创建它可以找到的pod。 我想知道音量是否没有正确分离。 现在我只是有一个奇怪的工作流程，将卷附加到随机实例，然后在更新容器图像时将其分离 

If I create this pod:
 
apiVersion: v1
kind: Pod
metadata:
name: dsm-manager
spec:
containers:
- name: dsm-manager
image: ******
imagePullPolicy: Always
command:
- /sbin/init
volumeMounts:
- mountPath: /srv/project/DSMManager/snapshots
name: dsm-snapshot-storage
volumes:
- name: dsm-snapshot-storage
awsElasticBlockStore:
volumeID: aws://us-west-2b/vol-43e44482
fsType: ext4
imagePullSecrets:
- name: dockerregistrykey
 
It always works, but if I delete it and re-create it it gets stuck with status 'CreatingContainer'. Looking in the events yields:
 -Unable to mount volumes for pod "dsm-manager_default": Timeout waiting for volume state
 -Error syncing pod, skipping: Timeout waiting for volume state
 
If I delete the pod and re-create it the same thing happens no matter what I do. However if I attach the volume to some instance and then detach it through the aws cli, then create the pod it works find. I'm wondering if the volume isn't being detached properly. For now I just have this odd work flow of attaching the volume to a random instance then detaching it while updating the container image

原文：https://stackoverflow.com/questions/32894930