I've changed the master-ip setting inside my master-config.yaml (which was still on the pub-ip of the installation). I replaced it with my private ip and restarted the cluster.
NAME ENDPOINTS AGE
kubernetes 192.168.20.1:8053,192.168.20.1:8443,192.168.20.1:8053 19h
I'm able to deploy my router + registry (images are pulled form a private registry in the same VLAN).
But I'm not able to authenticate on my registry. I didn't secure it yet.
docker login -u admin -e any mail com -p `oc whoami -t` 172.30.250.73:5000
Error response from daemon: no successful auth challenge for http://172.30.250.73:5000/v2/ - errors: [basic auth attempt to http://172.30.250.73:5000/v2/ realm "openshift" failed with status: 400 Bad Request]
Van: Clayton Coleman <ccoleman redhat com>
Verzonden: woensdag 7 december 2016 14:56:30
Aan: Den Cowboy
CC: users lists openshift redhat com
Onderwerp: Re: OpenShift origin cluster in VLAN
Each master still needs an IP registered that then backs the Kubernetes service that clients use to talk to the API. So verify that each master is reporting the correct IP that is reachable from all nodes to "oc get endpoints kubernetes -n defaults"
On Dec 7, 2016, at 9:39 AM, Den Cowboy <dencowboy hotmail com> wrote: