layout | title |
---|---|
default |
GlusterFS |
Steps to use GlusterFS in Kubernetes for Seldon.
Assumes you wish to create your glusterfs cluster in a separate VPC from Kubernetes so its lifetime is not connected to that of the Kubernetes cluster.
- Create an AWS VPC
- Ensure ip range does not overlap with Kubernetes default, e.g. use 192.*
- Create a GlusterFS cluster in VPC
- Two t2.micro instances minimum
- Create a Kubernetes Cluster
- Add glusterfs software for client to each minion and also master if you wish
- Create a VPC Peering connection in glusterFS VPC to Kubernetes VPC
- Create Peering connection and accept request.
- Edit glusterfs routing table to allow traffic to kubernetes
- There will be two routing tables. Choose the routing table with the subnet. Add the ip range for kubernetes (usually 172.20.0.0/16). Choose the Peering connection as destination.
- Edit kubernetes routing table to allow traffic to glusterfs
- There will be two routing tables. Choose the routing table with the subnet. Add the ip range for glusterfs (for example 192.168.0.0/16). Choose the Peering connection as destination.
- Update security group for glusterfs inbound to allow kubernetes traffic
- Update security group for kubernetes inbound to allow glusterfs traffic
- Test mount glusterfs volume on master or minion node, e.g.
mkdir /mnt/glusterfs
,mount.glusterfs 192.168.0.149:/gv0 /mnt/glusterfs
- Ensure you follow docs for glusterfs use in Seldon
Contributions welcome.