diff options
| author | Tyler Ramer <tyaramer@gmail.com> | 2020-03-27 13:33:37 -0400 |
|---|---|---|
| committer | Tyler Ramer <tyaramer@gmail.com> | 2020-03-27 13:33:37 -0400 |
| commit | d704144f530bd473556a018349e13d082bff4676 (patch) | |
| tree | 59fb8140d83ac240a9c1d910600c8de16da1287c /test/endpoint | |
| parent | ff0124aee1ca700be3b7357b992a220cdacfddfd (diff) | |
| download | podman-d704144f530bd473556a018349e13d082bff4676.tar.gz podman-d704144f530bd473556a018349e13d082bff4676.tar.bz2 podman-d704144f530bd473556a018349e13d082bff4676.zip | |
Sanitize port parsing for pods in play kube
The logic used in parsing the ports to be utilized in a kubenetes api
defined pod did not fully adhere to the kubenetes spec, nor did it map
well to a podman context. This fix sanitizes the input of container
ports to meet the following rules:
- A defined containerPort with no defined hostPort does nothing in a
podman context, or is informational. This is line with [usage in
Kubernetes.](https://github.com/kubernetes/kubernetes/issues/4332)
- A defined hostPort with no defined containerPort acts like a
publish [hostPort]:[hostPort]
- A defined containerPort and defined hostPort works like it does in
kubernetes, as in a publish [hostPort]:[containerPort]
Addresses https://github.com/containers/libpod/issues/5610
Signed-off-by: Tyler Ramer <tyaramer@gmail.com>
Diffstat (limited to 'test/endpoint')
0 files changed, 0 insertions, 0 deletions