Include port names in the 'minikube service' cmd's output

[11janci]

Extend the minikube service {service_name} command's output by adding a new column 'Target Port' for port names.

Pls note that currently the column is included always and will be empty if there are no node ports or target ports. Let me know if you'd like to hide it if empty, add a flag for showing it (as suggested in the linked issue), or rename the column's header.

Before

|-----------|---------------------|--------------|
| NAMESPACE |        NAME         |      URL     |
|-----------|---------------------|--------------|
| default   | kubernetes-bootcamp | No node port |
|-----------|---------------------|--------------|

After

|-----------|---------------------|-------------|--------------|
| NAMESPACE |        NAME         | TARGET PORT |     URL      |
|-----------|---------------------|-------------|--------------|
| default   | kubernetes-bootcamp |             | No node port |
|-----------|---------------------|-------------|--------------|

|-----------|-------------------|-------------|--------------------------------|
| NAMESPACE |       NAME        | TARGET PORT |              URL               |
|-----------|-------------------|-------------|--------------------------------|
| default   | nothing-minecraft | server      | http://192.168.99.100:32225    |
|           |                   | dynmap      | http://192.168.99.100:32412    |
|-----------|-------------------|-------------|--------------------------------|

Closes #5200

[k8s-ci-robot]

Hi @11janci. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[minikube-bot]

Can one of the admins verify this patch?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 11janci
To complete the pull request process, please assign ra489
You can assign the PR to them by writing /assign @ra489 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[11janci]

/assign @RA489

[tstromberg]

For clarification when reviewing UI changes, it's useful to have a "before" and "after" example. Do you mind adding a "before" example to your PR description?

[11janci]

For clarification when reviewing UI changes, it's useful to have a "before" and "after" example. Do you mind adding a "before" example to your PR description?

done