[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata
- First Post
- Replies
- Stats
-
Go to
- ----- 2026 -----
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
[
https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi...
]
Jiri Pechanec commented on JBIDE-21448:
---------------------------------------
{noformat}
docker inspect registry.access.redhat.com/jboss-eap-7/eap70-openshift
"ExposedPorts": {
"8080/tcp": {},
"8443/tcp": {},
"8778/tcp": {}
},
{noformat}
But if you run the pod with EAP it has management port available bound on localhost - port
9990. It is useful to be able to easily port-forward to such port too
Port Forwarding: Allow port-forwarding of ports not defined on pod
metadata
---------------------------------------------------------------------------
Key: JBIDE-21448
URL: https://issues.jboss.org/browse/JBIDE-21448
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Jiri Pechanec
Priority: Critical
Labels: openshift_v3, port_forwarding_wizard
Fix For: 4.5.0.AM2
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.2.3#72005)
3235
days inactive
3235
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
tags (0)
participants (1)
-
Jiri Pechanec (JIRA)