Oh, great. Thanks!

On Friday, August 25, 2017, <jamelseagra...@gmail.com> wrote:

> Sure. Turns out the node was trying to tag the provisioned EBS volume but
> was lacking the corresponding AWS role permissions to do that. Once I
> updated the role with the right permissions, everything worked.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q&A" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com <javascript:;>.
> To post to this group, send email to kubernetes-users@googlegroups.com
> <javascript:;>.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to