[jbosstools-issues] [JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

André Dietisheim (Jira) issues at jboss.org
Wed May 13 10:20:04 EDT 2020


    [ https://issues.redhat.com/browse/JBIDE-21448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095720#comment-14095720 ] 

André Dietisheim commented on JBIDE-21448:
------------------------------------------

Downgrading to major severity (was: critical). This is even more true since we plan to fade out this tooling and replace it by odo tooling.

> Port Forwarding: Allow port-forwarding of ports not defined on pod metadata
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-21448
>                 URL: https://issues.redhat.com/browse/JBIDE-21448
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.3.1.Beta1
>            Reporter: Jiri Pechanec
>            Priority: Major
>              Labels: openshift_v3, port_forwarding_wizard
>             Fix For: 4.16.x
>
>
> Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too.
> And example is EAP CLI



--
This message was sent by Atlassian Jira
(v7.13.8#713008)



More information about the jbosstools-issues mailing list