ASSERT: have a CDK3/minishift binary that's renamed (this makes sure that it wont inform about the docker registry making the tooling fall back to an erroneous default)
ASSERT: have a CDK3/minishift server adapter
ASSERT: make sure that you DONT have a connection to CDK3/minishift in the OpenShift Explorer
EXEC: launch CDK3/minishift server adapter
ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created
EXEC: in OpenShift explorer: pick "Edit Connection..."
ASSERT: connection wizard pops up
EXEC: hit "Advanced >>" and inspect "Image Registry URL"
ASSERT: have a CDK3/minishift binary that's renamed (this makes sure that it wont inform about the docker registry making the tooling fall back to an erroneous default)
ASSERT: have a CDK3/minishift server adapter
ASSERT: make sure that you DONT have a connection to CDK3/minishift in the OpenShift Explorer
EXEC: launch CDK3/minishift server adapter
ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created
EXEC: in OpenShift explorer: pick "Edit Connection..."
ASSERT: connection wizard pops up
EXEC: hit "Advanced >>" and inspect "Image Registry URL"
Result:
The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/
Expected result:
the correct value for the docker registry can be fetched from minishift by doing (in cmd-line):
./minishift openshift registry
In the current state of CDK3/minishift, where the docker registry is not publicly reachable, the correct value that is reported is an internal IP:
172.30.1.1:5000