[ https://issues.jboss.org/browse/JBIDE-21626?page=com.atlassian.jira.plugi... ] Jeff Cantrill edited comment on JBIDE-21626 at 2/25/16 5:14 PM: ---------------------------------------------------------------- [~fbricon] [~adietish] [~maxandersen] These changes I think smooth out the experience. It allows for * Creating resources even when we are unable to access the metadata. User must provide at least a service port * The repo/username/image will be referenced in the ImageStream There are no guarantees you will see a pod spin up for this deployment. This will ONLY happen if the server can pull the image. If the repo is not defined, normal docker semantics apply which is it tries dockerhub. The only variance to this is if the server docker registry is configured to default someplace else. was (Author: jcantrill): [~fbricon] [~adietish][~maxandersen] These changes I think smooth out the experience. It allows for * Creating resources even when we are unable to access the metadata. User must provide at least a service port * The repo/username/image will be referenced in the ImageStream There are no guarantees you will see a pod spin up for this deployment. This will ONLY happen if the server can pull the image. If the repo is not defined, normal docker semantics apply which is it tries dockerhub. The only variance to this is if the server docker registry is configured to default someplace else. -- This message was sent by Atlassian JIRA (v6.4.11#64026)