search

Project31 / ansible-kubernetes-openshift-pi3

Ansible playbooks for setting up a Kubernetes Raspberry Pi 3 cluster
190 stars 56 forks source link

persistentvolume-binder disabled by default #21

Closed SitoCH closed 7 years ago

SitoCH commented 7 years ago

Hi, is there a reason why the persistentvolume-binder is disabled by default?

roles/kubernetes/templates/kubeadm.yml:

controllers: "*,-persistentvolume-binder,bootstrapsigner,tokencleaner"

In my fork I'm using GlusterFS and I had to enable the persistentvolume-binder in order to bind PersistentVolumeClaims to PersistentVolumes. So I far I didn't have issues and my pod with MySQL is bound correctly.

Thank you

Sito

rhuss commented 7 years ago

Actually, I copied it over from https://github.com/luxas/kubeadm-workshop at that time without when I switched to kubeadm. As it seems in the current version it's not used anymore, so I'm perfectly fine with removing it.

Also, when time permits, I'm going to upgrade to the latest and greatest version of @luxas workshop.

luxas commented 7 years ago

@rhuss I'm updating kubeadm-workshop to be ready for v1.7, will be ready any day after v1.7.0 is out.

There's no need to disable that controller anymore; I disabled it in the main controller-manager but enabled it in an extra controller-manager on top of Kubernetes using a different base image. Why?

Because I used rbd for Dynamic Storage Provisioning and rbd shells out to the binary with the same name and the fact the vanilla controller-manager image is based on busybox with no rbd, I had to workaround it that way.

Stay tuned and oing me if I forget to report more here :)

rhuss commented 7 years ago

@luxas thanks a lot for the update and your awesome work on kubeadm !

SitoCH commented 7 years ago

Perfect, at the moment I'm using the persistentvolume-binder with GlusterFS without issues. Everything is a bit slow but it's great for experimenting websites with MySQL as a database, all packed inside the cluster.