mirror of https://github.com/containers/podman.git
f35d1c1c25
When InitialDelaySeconds in the kube yaml is set for a helthcheck, don't update the healthcheck status till those initial delay seconds are over. We were waiting to update for a failing healtcheck, but when the healthcheck was successful during the initial delay time, the status was being updated as healthy immediately. This is misleading to the users wondering why their healthcheck takes much longer to fail for a failing case while it is quick to succeed for a healthy case. It also doesn't match what the k8s InitialDelaySeconds does. This change is only for kube play, podman healthcheck run is unaffected. Signed-off-by: Urvashi Mohnani <umohnani@redhat.com> |
||
|---|---|---|
| .. | ||
| annotations.go | ||
| autoupdate.go | ||
| checkpoint_restore.go | ||
| config.go | ||
| container.go | ||
| container_inspect.go | ||
| containerstate.go | ||
| diff.go | ||
| errors.go | ||
| exec_codes.go | ||
| exit_code_propagation.go | ||
| fileinfo.go | ||
| healthchecks.go | ||
| info.go | ||
| mount.go | ||
| mount_freebsd.go | ||
| mount_linux.go | ||
| mount_unsupported.go | ||
| pod_inspect.go | ||
| podstate.go | ||
| runtime.go | ||
| sdnotify.go | ||
| version.go | ||
| volume_inspect.go | ||