OpenShift Origin on Minikube

[MNS]

Hi,

I've been trying to spin up an OpenShift Origin setup on Minikube using the example here. (I'm aware of minishift, but my prod deployment target is GKE, so I prefer the openshift on k8s approach)

After going through the steps and tweaking a few things here and there (eg. using the .minikube key/certs for the admin/kubeconfig), I managed to generate the secrets so that  the openshift master starts, however it's not  able to connect to the kubernetes api server:

2017-03-05T17:39:15.237586284Z I0305 17:39:15.237458       1 start_master.go:422] Starting master on 0.0.0.0:8443 (v1.5.0-alpha.3+2261a32-234)

2017-03-05T17:39:15.237760743Z I0305 17:39:15.237704       1 start_master.go:423] Public master address is https://192.168.99.100:8443

2017-03-05T17:39:15.237843404Z I0305 17:39:15.237788       1 start_master.go:427] Using images from "openshift/origin-<component>:v1.5.0-alpha.3"

2017-03-05T17:39:15.241814976Z E0305 17:39:15.241678       1 reflector.go:199] github.com/openshift/origin/vendor/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:103: Failed to list *api.ServiceAccount: Get https://localhost:8443/api/v1/serviceaccounts?resourceVersion=0: dial tcp [::1]:8443: getsockopt: connection refused

2017-03-05T17:39:15.242051240Z E0305 17:39:15.241927       1 reflector.go:199] github.com/openshift/origin/vendor/k8s.io/kubernetes/plugin/pkg/admission/storageclass/default/admission.go:75: Failed to list *storage.StorageClass: Get https://localhost:8443/apis/storage.k8s.io/v1beta1/storageclasses?resourceVersion=0: dial tcp [::1]:8443: getsockopt: connection refused

Has anyone managed to get openshift running on minikube and could share some pointers?

Thanks, Mark

[Matthew L Daniel]

The change appears to be that when it says "start master --write-config blah-blah --master=https://localhost:8443" you'll want to not use "localhost:8443", but instead use  https://kubernetes or via its IP, if the API cert has an IP SubjectAlternateName; the IP should be fixed, but is also present in ${KUBERNETES_SERVICE_HOST}

After I made that change, I still received service account authentication errors, because something isn't squared up with the certs it is using versus the certs I provided, but hopefully you'll have better luck troubleshooting that step than where you are now.

  HTH,

  -- /v\atthew