You should be able to do fully out-of-tree external provisioning without CSI. I think other vendors do it. Run a controller that watches PVCs, and filters for your class name. React to state changes there.
On Sun, Oct 15, 2017 at 5:01 PM, <adi...@portworx.com> wrote: > Thanks Tim for your help. > > The attach/detach controller will solve the problem of Setup and Teardown of > Pods with PVs. However we face this issue with provisioning of volumes. > > As PVC create operation is issued by master, we need some way for the master > to talk to Portworx pods. Until CSI is implemented in Kubernetes, do you have > any suggestion to overcome this problem? > > > On Sunday, October 15, 2017 at 2:56:44 PM UTC-7, Tim Hockin wrote: >> In general the control plane can not access Services. Not all installations >> treat the master as a node, and it's not actually required to be. >> >> >> Consider that the controller manager is responsible for telling resolving >> services to endpoints - having g it depends on service cluster IPs depends >> on endpoints. Somewhat (perhaps not quite literally) circular. >> >> >> Additionally, the GKE master lives in a distinct network segment from the >> nodes, speaking over (for now) public IP. >> >> >> This yet another reason why moving storage drivers out of core is important. >> Saad has a loose plan to move attach/detach into a controller that runs in >> cluster. >> >> >> Tim >> >> >> On Oct 15, 2017 12:45 PM, <adi...@portworx.com> wrote: >> Can someone help us here? >> >> Basically the Kubernetes controller manager on GKE is unable to reach the >> Service. Is something different required in case of GKE in the service >> description? >> >> >> >> >> >> >> On Tuesday, June 27, 2017 at 2:48:31 PM UTC-7, ha...@portworx.com wrote: >> >> > I deployed GKE 1.6.6 and ran a Service with a Cluster IP (in the >> > kube-system namespace). >> >> > >> >> > The hosted Kubernetes controller manager on GKE is unable to reach our >> > service over the cluster IP. All minions on GKE can reach the service but >> > the hosted controller manager cannot. >> >> > >> >> > This behavior is different from what's seen on other 1.6.6 installations >> > like kubeadm where the kubernetes controller manager is able to reach the >> > same service. >> >> > >> >> > Details on the Service: >> >> > ====================== >> >> > >> >> > The service being deployed is a Portworx volume plugin service >> > (https://docs.portworx.com/scheduler/kubernetes/install.html#install) with >> > following spec. I'm not including the Pod definitions for sake of brevity >> > (the issue here is the service itself is not reachable). >> >> > >> >> > kind: Service >> >> > apiVersion: v1 >> >> > metadata: >> >> > name: portworx-service >> >> > namespace: kube-system >> >> > spec: >> >> > selector: >> >> > name: portworx >> >> > ports: >> >> > - protocol: TCP >> >> > port: 9001 >> >> > targetPort: 9001 >> >> > >> >> > This service is used by the native Portworx volume plugin which is in the >> > kubernetes code base and runs within the controller manager. >> >> > >> >> > Would appreciate any help on what I'm missing and what should be the >> > expected behavior. >> >> > >> >> > Thanks! >> >> >> >> -- >> >> 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-use...@googlegroups.com. >> >> To post to this group, send email to kubernet...@googlegroups.com. >> >> 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. -- 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.
