Podman kube play assumes port numbers in liveness probe

[hedayat]

Issue Description

Currently, when using Kubernetes liveness probes, podman assumes that Http/TCP port number is given in the probe, while you can use port name instead. Podman should check if the livenessProbe.tcpSocket.port (and the equivalent HTTP one) is an string or a number, and if it is a string try to interpret it as a port name given in ports.name (which is checked as supported in podman-kube-play man page).

Steps to reproduce the issue

Steps to reproduce the issue

1. Use a Kybernetes YAML with livenessProbe.tcpSocket.port as a port name
2. Run the pod using podman kube play, and then inspect the resulting pod
3. The port in the given nc command is 0 (And the corresponding source code explicitly converts to Port to IntValue).

Describe the results you received

0 port number used

Describe the results you expected

The port number corresponding to the port name should be used instead.

podman info output

Tested with podman 4.5.0

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

[rhatdan]

Interested in opening a PR to fix?

[rhatdan]

@umohnani8 PTAL

[hedayat]

Interested in opening a PR to fix?

Can't promise right now, but might take a look soon if it was not fixed till then :)

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

@hedayat @umohnani8 still an issue.

[rhatdan]

@Luap99 Interested in taking a look?

[hedayat]

I'm on it.