The blocker I found was that these clusters run Debian, currently 7.9 or more specifically "Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64". Can't install clusterhq-flocker-node and clusterhq-flocker-docker-plugin on that, or can I?
regards /Staffan
Ryan Wallner
unread,
Apr 25, 2016, 8:52:07 AM4/25/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to flocker-users
Hi Steffan,
This would be great, and yes the flavor used by the nodes in GKE would likely mean you would need to install Flocker using our docker images. E.g. `docker run flocker-dataset-agent` and for the rest of them.
Keep in mind that the docs at the link above are slightly outdated, you can find updated commands in the PR which is merged and will be in the next docs release it looks like.
In the future we may look at GKE support, I will make a note of your interest, we appreciate your feedback!
Staffan Olsson
unread,
Aug 6, 2016, 3:17:48 PM8/6/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to flocker-users
Hi,
Once again I'm evaluating the options for high-availability persistent volumes on GKE. It's notable at http://kubernetes.io/docs/user-guide/persistent-volumes/#access-modes that both AWS and Azure have "ReadWriteMany" options for storage (NFS and azureFile respectively), but Google Container Engine does not.