odo inside DevSpaces: forwarded ports not detected by Port Extension

[kadel]

/kind bug

I have encountered an issue arising when using odo inside of DevSpaces. Normally when a process inside of a DevSpaces workspace opens a port, the Port extension realizes this, shows a prompt to publish the URL externally. This works great for example when starting Quarkus in dev mode
mvn quarkus:dev
But when running odo 3
odo dev
which now works by tunneling a local ports 40001 and 40002 to the OpenShift service, Port extension does not pick this up, so there are no Routes published in DevSpaces and hence you cannot access the running app.

What versions of software are you using?

Operating System:

Output of odo version:

How did you run odo exactly?

Actual behavior

Expected behavior

Any logs, error output, etc?

[kadel]

From quick research, it looks like it is related to the port numbers.

If I change quarkus to listen on 40001, the port is not detected.

a quick way to test it is using python

python -m http.server 8080

8080 - detected
7000 - detected
30000 - detected
40000 - not detected
31000 - detected
32000 - not detected
31900 - detected
31999 - detected
32000 - not detected

from testing, it looks like it checks only for ports < 32000

[kadel]

Created two user stories to address this

• Change port range used for port-forwarding endpoints #6483
• Allow users define custom port-mappings for port forwarding #6479

[rm3l]

/close

Issue fixed via #6483

[openshift-ci]

@rm3l: Closing this issue.

In response to this:

/close

Issue fixed via #6483

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.