[
https://issues.jboss.org/browse/JBIDE-21228?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-21228:
---------------------------------------
The specific value pointed to here is what the server substitutes into the DC based on how
it is originally defined; if its pointed to an actual image, imagestreamtag, etc.
Additionally, the 'openshift' namespace is special in that it is a library of
various resources. How was this 'app' created? My guess is it was deployed by
falling back to the image that was in the openshift namespace. If that was the case, this
DC looks as I would expect.
DeploymentConfig for Deploying a docker image should point the image
container to the imagestream
-------------------------------------------------------------------------------------------------
Key: JBIDE-21228
URL:
https://issues.jboss.org/browse/JBIDE-21228
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Labels: openshift_v3
Fix For: 4.4.0.Alpha1
Deploying a docker image from a local machine will create resources. When the image is
pushed to OS, the DC should assume it will be namespaced to the same project in which the
resources are created. Ref:
https://gist.github.com/jcantrill/cb84b919e1a7a4791440#file-gistfile1-txt...
This image was deployed to the 'helloworld' namespace and the image spec should
not include the original docker namespace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)