Test on AWS

[suchisubhra]

i am testing Petset first time.. After running this in my cluster on AWS,

I am getting this error

kubectl1.3 escribe pods etcd

1h 24s 245 {default-scheduler } Warning FailedScheduling [PersistentVolumeClaim is not bound: "data-etcd-0", PersistentVolumeClaim is not bound: "data-etcd-0"]

Further investigation shows kubectl1.3 describe pvc data-etcd-1 1h 0s 289 {persistentvolume-controller } Warning ProvisioningFailed No provisioner plugin found for the claim!

Pretty sure I a m doing something wrong. But no able to figure out where I can set up this plugin Any help appreciated

[Ulexus]

Yeah, you are missing the AWS ElasticBlockStore provisioner in your kubernetes setup, it would seem. How did you set up this kubernetes cluster?

[suchisubhra]

I use terraform...

On Thu, Sep 1, 2016 at 3:14 PM, Seán C. McCord notifications@github.com wrote:

Yeah, you are missing the AWS ElasticBlockStore provisioner in your kubernetes setup, it would seem. How did you set up this kubernetes cluster?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CyCoreSystems/etcd-petset/issues/1#issuecomment-244229085, or mute the thread https://github.com/notifications/unsubscribe-auth/AFZ3zYaG-rwshviE-VuJMQDpsIlfcfcJks5ql040gaJpZM4JzITd .

~suchi

To the optimist, the glass is half full.To the pessimist, the glass is half empty.To the engineer, the glass is twice as big as it needs to be.

[Ulexus]

I don't know anything about HashiCorp's stack, but that's what that message is indicating: it can't provision the EBS volume because the plugin to do so is not found.

[suchisubhra]

where do you define the plugin.. is it not part of kubernetes package? Or i have to install it separately..

I am not able to find out any doc on dynamic provisioning

~Suchi

On Thu, Sep 1, 2016 at 3:22 PM, Seán C. McCord notifications@github.com wrote:

I don't know anything about HashiCorp's stack, but that's what that message is indicating: it can't provision the EBS volume because the plugin to do so is not found.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CyCoreSystems/etcd-petset/issues/1#issuecomment-244230738, or mute the thread https://github.com/notifications/unsubscribe-auth/AFZ3zQPMNAO6WxCRokRd-1twDsVA5LDSks5ql1AIgaJpZM4JzITd .

~suchi

To the optimist, the glass is half full.To the pessimist, the glass is half empty.To the engineer, the glass is twice as big as it needs to be.

[suchisubhra]

One more question,, do you create PV and PVC before running etcd.yaml or you scripts creates those volumes..

My assumption.. volumes are created dynamically after you run your script...

~Suchi

On Thu, Sep 1, 2016 at 3:25 PM, Suchisubhra suchisubhra@gmail.com wrote:

where do you define the plugin.. is it not part of kubernetes package? Or i have to install it separately..

I am not able to find out any doc on dynamic provisioning

~Suchi

On Thu, Sep 1, 2016 at 3:22 PM, Seán C. McCord notifications@github.com wrote:

I don't know anything about HashiCorp's stack, but that's what that message is indicating: it can't provision the EBS volume because the plugin to do so is not found.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CyCoreSystems/etcd-petset/issues/1#issuecomment-244230738, or mute the thread https://github.com/notifications/unsubscribe-auth/AFZ3zQPMNAO6WxCRokRd-1twDsVA5LDSks5ql1AIgaJpZM4JzITd .

~suchi

To the optimist, the glass is half full.To the pessimist, the glass is half empty.To the engineer, the glass is twice as big as it needs to be.

~suchi

To the optimist, the glass is half full.To the pessimist, the glass is half empty.To the engineer, the glass is twice as big as it needs to be.

[Ulexus]

The current dynamic provisioning is a bit of a kludge. Kubernetes 1.4 will have a bit more formalized approach.

If you are running on a supported platform (which AWS should be), the PVs and PVCs should be created automatically, but that is not happening for you. You certainly can manually define your PVs and PVCs; just keep the same PVC names that the dynamic provisioner would make (data-etcd-0, data-etcd-1, etc).