Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-24491

CDK Server adapter: allow users to look up the address of the docker registry

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 4.5.1.Final
    • 4.4.4.Final
    • cdk
    • None

    Description

      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 

      ./minishift openshift registry

      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.

      Attachments

        Issue Links

          is duplicated by

          Sub-task - The sub-task of the issue JBIDE-24650 Modify tooling UI to invoke command to retrieve the Docker registry

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users JBIDE-25093 IT: create tests for the Docker discovery feature

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-25046 Can't find CDK for registry discovery when 2 connections are defined for CDK

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-25049 Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-25047 Connection wizard: correct advanced buttons to be equal in width

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: