imagestream is always using the registry ip instead of registry hostname

[thincal]

If I push an image for example registry.example.com:5000/default/hello-openshift to the integrated registry, at the same time an imagestream will be created automatically, but oc get is shows:

NAME              DOCKER REPO                                   TAGS      UPDATED
hello-openshift   172.30.117.244:5000/default/hello-openshift   latest    7 minutes ago

When I create a pod referring the image registry.example.com:5000/default/hello-openshift, it will report the error:

Failed to pull image "registry.example.com:5000/default/hello-openshift:latest": image pull failed for registry.example.com:5000/default/hello-openshift:latest, this may be because there are no credentials on this request. details: (Error: image default/hello-openshift:latest not found) 

So what the reason to use the registry ip in the imagestream instead of the registry hostname even if I push the image formatted like as hostname:port/project/imagename ? or is this the bug simply ?

This issue is confusing me several days about the image pull failure when creating the pod, after using the registry-ip:port/project/imagename pod is created successfully.

[thincal]

And since the registry service's IP could be changed, so if referring the IP in the imagestream, is that good ?

for example:

$ oc get is
NAME                              DOCKER REPO                                                     TAGS                         UPDATED
hello-openshift                   172.30.117.244:5000/openshift/hello-openshift                   latest                       2 days ago

why not:

$ oc get is
NAME                              DOCKER REPO                                                     TAGS                         UPDATED
hello-openshift                   registry.example.com:5000/openshift/hello-openshift                   latest                       2 days ago

[thincal]

@soltysh so is this by design ?

[soltysh]

Unfortunately for now it is, but I'm going to work on it. I can't promise
when, though, but I'll try as soon as possible.
On Dec 16, 2015 6:00 PM, "LS" notifications@github.com wrote:

@soltysh https://github.com/soltysh so is this by design ?

—
Reply to this email directly or view it on GitHub
#6283 (comment).

[liggitt]

switching to hostname requires changes to the dockercfgs we generate before pulls will work. @deads2k

[deads2k]

switching to hostname requires changes to the dockercfgs we generate before pulls will work. @deads2k

I'm looking at it.

[thincal]

@deads2k any comments so far with this question ?

[liggitt]

Changes to credential generation are in progress but won't be completed until the new year

[liggitt]

Once that is done, the image stream resolution could be changed to use DNS instead of IP. That would add a dns resolution requirement for services to the nodes. I'm not positive that is required today, so that may be a new requirement.

[thincal]

Thanks for your update.

That would add a dns resolution requirement for services to the nodes.

I don't understand this quite well, since the registry hostname resolution to IP is done by external DNS server, what do you mean about here? thanks.