kubectl: add port names to describe pod output

[rushmash91]

What type of PR is this?
/kind feature
/sig cli

What this PR does / why we need it:
Adds port names to kubectl describe pod output to make it easier to identify port purposes without referencing the original manifest.

Which issue(s) this PR fixes:
Fixes kubernetes/kubectl#1755

Special notes for your reviewer:
This change only affects the display formatting of container ports in describe output. The logic gracefully handles both named and unnamed ports.

When describing pods, include port names alongside port numbers to make it easier to identify port purposes without referencing the original manifest.

Example output:

Ports: 80/TCP (http), 443/TCP (https)

This eliminates work when creating services or understanding port purposes, especially for external resources deployed via helm charts.

Does this PR introduce a user-facing change?

kubectl: `describe pod` now includes port names alongside port numbers (e.g., "80/TCP (http)") when port names are specified in the pod spec.

[linux-foundation-easycla]

• ✅login: rushmash91 / (1d0fd59)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @rushmash91!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @rushmash91. 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.

Details

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-sigs/prow repository.

[a-hilaly]

/ok-to-test

[a-hilaly]

Thanks @rushmash91 !

[a-hilaly]

cc @dims @eddiezane

[mpuckett159]

/assign

[ardaguclu]

/triage accepted
/priority backlog
/label release-note

[k8s-ci-robot]

@ardaguclu: The label(s) /label release-note cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full, official-cve-feed. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/triage accepted
/priority backlog
/label release-note

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-sigs/prow repository.

[ardaguclu]

/priority backlog
/release-note

[k8s-ci-robot]

@ardaguclu: the /release-note and /release-note-action-required commands have been deprecated.
Please edit the release-note block in the PR body text to include the release note. If the release note requires additional action include the string action required in the release note. For example:

```release-note
Some release note with action required.
```

Details

In response to this:

/priority backlog
/release-note

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-sigs/prow repository.

[ardaguclu]

/priority backlog
/release-note describe pod now includes port names alongside port numbers (e.g., "80/TCP (http)") when port names are specified in the pod spec.

[ardaguclu]

/release-note "describe pod now includes port names alongside port numbers (e.g., "80/TCP (http)") when port names are specified in the pod spec."

[ardaguclu]

/release-note "describe pod now includes port names alongside port numbers"

[ardaguclu]

/release-note-none

[ardaguclu]

That looks nice, thank you
/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: be430d32883f49dc68e45ba6d4bf469831ce4b31

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a-hilaly, ardaguclu, rushmash91

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• staging/src/k8s.io/kubectl/OWNERS [ardaguclu]

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