[
https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-24491:
---------------------------------------
{quote}<agupta> jcantril, ops deploys the registry... and defines the route for
external access..
<jcantril> agupta, but there is no way to discover the route?
<agupta> jcantril, this will need inputs from registry folks (n/w team)..
<agupta> jcantril, the URL has a fixed format, though...
registry.<clusterid>.openshift.com
<agupta> jcantril, we don't currently document this format.. reached out to
ahardin for that
<jcantril> agupta, there is no way for ave. use to query for the route either right?
since it probably lives in the default namespace?
<agupta> jcantril, that is correct..{quote}.
CDK Server adapter: allow users to look up the address of the docker
registry
-----------------------------------------------------------------------------
Key: JBIDE-24491
URL:
https://issues.jboss.org/browse/JBIDE-24491
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.4.Final
Reporter: Andre Dietisheim
if you want to push a docker image to the docker registry within OpenShift you need the
address of the docker registry.
When launching the cdk in Eclipse our tooling creates the OpenShift connection for the
tooling filling out that address.
Users that didnt launch the cdk via the server adapter or had their connection already
defined when launching it, would have to look the address up manually. One does this on
the command line via {code}./minishift openshift registry{code}
It would be nice if the server adapter would offer a way to look it up so that the user
does not have to go the command line.
I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)