@vzhukovs looks like the description of the issue is empty and not matching our templates

@benoitf I've updated the issue description to met the current requirements

With regards to UI, we'll most likely have to add it as well as a separate section similar to how we list services, deployments, etc.

This is usually standard on other UI's as well I've seen.

With regards to UI, we'll most likely have to add it as well as a separate section similar to how we list services, deployments, etc.

This is usually standard on other UI's as well I've seen.

Yep, it definitely should be a dedicated page on the UI to manage the forwards. The main idea is to have the list of forwards with start/stop and edit/delete buttons on each item. In the top there can be a create button that will open a form to create a new forward with necessary input fields. Each item in the list can represent a single port mapping or a bulk one. A bit later will try to make some mockups for it to have agree on the final UI version.

@vzhukovs I also want to ask if we will be supporting any controller / service / pod?

Looking through the kubectl port-forward --help, it supports doing port forwarding on a deployment, pod and service.

I'm assuming we'll be adding it as an action to all of them?

I also want to ask if we will be supporting any controller / service / pod?

@cdrage the backend code supports forwarding ports from pods, deployments, services (simple numeric ports and named ports), the only one limitation at this moment is that everything forwards to localhost, passing different host address will be implemented in the future PRs. It depends, what workload kind we will pass to the backend side from the UI.

The main idea is to allow user to select where ports will be taken to forward. Some kind of selection input in create forward configuration dialog.