text: Title: EBS in AWS clusters is all about issues and headaches
  Body: Using EBS volumes is way too unstable on k8s aws deployments, we've been using kubernetes since version 1.2, now running a 1.5.2 cluster and the problems have always been there and never solved.
  80% of the time I need to delete a pod under a replication controller or deployment that have a PVC linked it, it does not work, the problem varies, sometimes I saw this same message:
  
  ```
  I0213 16:49:05.844132       6 aws.go:1366] Waiting for volume "vol-a60ecccc" state: actual=attaching, desired=attached
  ```
  
  repeatedly for hours and some other times this another messages:
  
  ```
  I0213 16:49:05.844132       6 aws.go:1366] Waiting for volume "vol-a60e9901" state: actual=detached, desired=attached
  ```
  
  also for hours. The problem is only solved by deleting the pods several times, attaching and detaching the ebs manually through aws console several times, till it decides to work.
  
  The problem is so recurrent that we've now started to use EFS through NFS when we need persistent storage.
  
  I hope this gets fixed in future releases of kubernetes because it is disencouraging our team to run some applications that needs persistent volumes under k8s.