Documentation conflict regarding postStart

[jjulien]

This is a Bug Report

Problem:
Documentation exists that states a container enters a "running" status prior to executing "postStart" hooks. Other documentation, and observed behavior, states a pod does not enter a "running" status until after "postStart" hooks complete.

Proposed Solution:
Fix the documentation to reflect current behavior.

Currently reads

Once a container enters into Running, postStart hook (if any) is executed. This state also displays the time when the container entered Running state.

Should read

The postStart hook (if any) is executed prior to the container entering a Running state. This state also displays the time when the container entered Running state.

Current observed behavior is documented here
https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/#discussion

The Container’s status is not set to RUNNING until the postStart handler completes.

Page to Update:
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-states

[sftim]

@jjulien would you be willing to replace the pictures of hyperlinks with the URLs as text? That'll help people who want to follow those links.

(you can edit the description of your issue)

[jjulien]

Yea, I don't know what was going on when I created this. It automatically created those images when I tried to paste in the URLs. They should work now.

[sftim]

Thanks @jjulien
/priority backlog
/good-first-issue

[k8s-ci-robot]

@sftim:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Thanks @jjulien
/priority backlog
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rajattrt]

I will try to pick this one.
/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[rajattrt]

/close

[k8s-ci-robot]

@rajattrt: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.