Port-Forwarding support seems incomplete

[spyro2000]

I really would love to use the integrated port-forwarding. But It's lacking two important features to be actually useful for me:

• Not possible to manually set the local port to same or manual ** Random ports renders all my browser bookmarks and postman collections useless
• Not possible to manually specifiy source port
• For some reason, port 5005 for remote debugging doesn't show up while it is indeed working with kubectl via kubectl -n std port-forward my-pod-name 5005

[dkapanidis]

Hi,

thanks for your feedback. we started with an initial implementation and a simple UI to start with, now that we have the primitives in place the rest is part of finding the best UX. We try to avoid bloating the UI with too many buttons and whistles, and only add the necessary.

We can add a dropdown option on the same button to select different strategies of port-forwarding.

The use-same-port-as-local-port is a typical case that helps with the bookmarks and postman examples, and we'll definitely add it in the future.

The set manual port is more tedious process to do (you'd need to type in the port number) so you don't gain much by doing in the UI, you can use the kubectl for that at least for now. The primary focus on Kubernetic is productivity gain.

As for the specifying source port, in order for the port to be listed you need to define it in your Pod manifest ports list. If it is not there then it will not appear on Kubernetic.

[dkapanidis]

On the other hand we'll also be adding port-forwarding on other resources:

• bring all the deployment's ports locally (pick random pod)
• bring all the service's ports locally (load balanced pods)

[spyro2000]

Hi @dkapanidis,

this sounds great. Looking forward to it.