[jbosstools-issues] [JBoss JIRA] (JBIDE-22314) Define Docker registry URL for an OpenShift connection

[Hardy Ferentschik (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203086#comment-13203086 ] 

Hardy Ferentschik commented on JBIDE-22314:
-------------------------------------------

I guess there are two ways to go about this.

# Add the openshift-dev to the cluster:readers (or similar) group. Preferably we make sure that any basic user on the CDK would have the same privileges. This might be helpful for other resources the dev might want to view. 
# Extend the _vagrant-service-manager_ plugin to expose the registry information as well, eg as part of {{vagrant service-manager env openshift}}. 

> Define Docker registry URL for an OpenShift connection
> ------------------------------------------------------
>
>                 Key: JBIDE-22314
>                 URL: https://issues.jboss.org/browse/JBIDE-22314
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: openshift
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Fred Bricon
>            Assignee: Jeff Cantrill
>             Fix For: 4.4.0.Alpha2
>
>
> When deploying a docker image to openshift, we'll need to know where to push the docker image to.
> That docker registry url could be set from the OpenShift Connection wizard, in an advanced section.
> For the CDK, that url (hub.openshift.rhel-cdk.10.1.2.2.xip.io) is defined in a docker-registry route in the default project, which only admin can have access to. I don't know of any way to access that URL for a non-admin. Perhaps that url could be/is exposed by the vagrant service manager plugin? [~hardy.ferentschik]? [~rob.stryker]?
> In any case, an other url could be defined manually for non-CDK-based openshift instances



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)