What happened?

The comments in

Exposing a port here gives
the system additional information about the network connections a
container uses, but is primarily informational.

However there are several cases where this is false :

• When using a Service with a targetPort that references a name in the ports arrays of the pod.
• Some software (ab)uses this API to get which ports are used (See Patching ports in PodSpec leads to empty diff #108131 Although unfixable, my goal is to fix the documentation so other people don't have the same problem). The Azure Load Balancer implementation does this for instance.
• Some other network/security software might use this information.

Also, is it possible to document/reference the above issue in the comment ?

What did you expect to happen?

Since it is described as informational I expected for the network to work without this information. But it's definitely not the case.

How can we reproduce it (as minimally and precisely as possible)?

Not needed since it's mostly a doc issue.

Anything else we need to know?

I'm interested in contributing this patch but would like some feedbacks before doing it. :)

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)