While containers configured with healthcheck or livenessCheck with podman play kube, the container is not restarted. This looks like a followup to #14505 where a "healthcheck restart capability" is mentioned. I only could find --health-on-failure, which is probably what I am looking for, but I cannot find this option in podman play kube or what option in the kubernetes-file should be set to achieve this.
Issue Description
While containers configured with healthcheck or livenessCheck with
podman play kube
, the container is not restarted. This looks like a followup to #14505 where a "healthcheck restart capability" is mentioned. I only could find--health-on-failure
, which is probably what I am looking for, but I cannot find this option inpodman play kube
or what option in the kubernetes-file should be set to achieve this.Steps to reproduce the issue
Steps to reproduce the issue
exec-liveness.yaml
from https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/probe/exec-liveness.yamlpodman play kube exec-liveness.yaml
watch podman ps
unhealthy
after ~45 (30 seconds + 3 attempts)podman healthcheck run
followed by the container id observed frompodman ps
Describe the results you received
The container continued running. After 10 minutes the container is restarted, as the container command is terminated after 600 seconds.
Describe the results you expected
The container should have been restarted after it went unhealthy
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Running as unprivileged user on a VM (proxmox) with RHEL 9.1
Additional information
No response