The comments in
// List of ports to expose from the container. Exposing a port here givessays that :
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 :
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 hereCloud 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 hereInstall tools Container runtime (CRI) and and version (if applicable) Related plugins (CNI, CSI, ...) and versions (if applicable)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4