[jbosstools-issues] [JBoss JIRA] (JBIDE-23490) Server adapter: 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=13365966#comment-13365966 ] 

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

[~adietish] correct. Even if you would try to edit route to point to a pod instead of a service, OpenShift would not allow it. It would result into an error. Basically in hierarchy is Pod --> Service ---> Route. By exposing a pod you get a service which point to all relevant pods (specified by a selector). And by exposing a Service you get a routing to manage traffic to pods via pointing to a service. 

I am still not sure why there is a need of having a Server adapter pointing to a pod instead of a Service. Pods are volatile, but they are managed by replication controller so there is still a pod for application if needed. And to easily access an application we have a service which always know which pods belong to app. By pointing a server adapter to a pod we could throw away all what OpenShift offer. It would basically get down to a docker level - plain containers without orchestration, management... If server adapter would work for a pod instead of service there are other issues linked to the nature of pods - restarting in debug would make it unusable (it starts different pod), scaling won't be possible (there is a Service for it to point to multiple pods). I am replying because in the document (Fuse Integration Services and its integration to OpenShift) I haven't seen any answer since 11/2016 when I last time was wondering why is this "workflow" desired.

> Server adapter: 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, openshift_v3, server_adapter, server_adapter_wizard
>             Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds​ when there is no service provided.



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