[jbosstools-issues] [JBoss JIRA] (JBIDE-23490) Provide ability to link pods when no service is available

[Marián Labuda (JIRA)]

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

Marián Labuda commented on JBIDE-23490:
---------------------------------------

The description is too vague to find out what you wanted to have done here (I had and still dont have idea from description that you wanted to create a connection between server adapter and a pod).

Also I think it is not good enough to link a server adapter to a pod, because you would limit yourself too much. Pods are usually managed by OpenShift itself. Deployment configuration and replication controller take care about running pod. If you want to change something internally in a pod, you would have to respin another one. Or triggering debugging. Or scaling app by spinning up more pods. And if you would link server adapter to specific pod, you would be damned bcs. once you change something in deployment, you would have to reestablish connection between adapter and a pod. My 2 cents.

> Provide ability to link pods when no service is available
> ---------------------------------------------------------
>
>                 Key: JBIDE-23490
>                 URL: https://issues.jboss.org/browse/JBIDE-23490
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.4.2.AM3
>            Reporter: Aurélien Pupier
>            Assignee: Jeff MAURY
>              Labels: new_and_noteworthy
>             Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a pod to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds​



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)