Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mismatch in documentation about postStart script #85766

Open
HappyStoic opened this issue Nov 30, 2019 · 2 comments

Comments

@HappyStoic
Copy link

@HappyStoic HappyStoic commented Nov 30, 2019

Hello,
while browsing through the documentaion I found these two information:

Pod lifecycle docs

  • Running: Indicates that the container is executing without issues. Once a container enters into Running, postStart hook (if any) is executed. This state also displays the time when the container entered Running state.

Lifecycle events docs

  • The postStart handler runs asynchronously relative to the Container’s code, but Kubernetes’ management of the container blocks until the postStart handler completes. The Container’s status is not set to RUNNING until the postStart handler completes.

I find this mismatching and do not actually know which one is correct.

@HappyStoic

This comment has been minimized.

Copy link
Author

@HappyStoic HappyStoic commented Nov 30, 2019

/sig docs

@k8s-ci-robot k8s-ci-robot added sig/docs and removed needs-sig labels Nov 30, 2019
@udit249

This comment has been minimized.

Copy link

@udit249 udit249 commented Dec 2, 2019

I am working on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.