You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When I try to configure a TCP port forward for a pod, if the Target port is not listed it is impossible to force it to a value.
Describe the solution you'd like
I don't know how the autodiscovery of open port is done, but in this particular case I have a dynamic port opened occasionally on a development pod, I want to forward it and I can't.
I simply wish it was possible to force a Target port even if it is unlisted.
Here an image of my case
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When I try to configure a TCP port forward for a pod, if the Target port is not listed it is impossible to force it to a value.
Describe the solution you'd like
I don't know how the autodiscovery of open port is done, but in this particular case I have a dynamic port opened occasionally on a development pod, I want to forward it and I can't.
I simply wish it was possible to force a Target port even if it is unlisted.
Here an image of my case
The text was updated successfully, but these errors were encountered: