Open pulkits15 opened 1 year ago
Page related to issue: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/ /language en
/retitle Improve clarity on synchronous and asynchronous nature of Container hooks handlers
You can find the information and the entire paragraph on the Page: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#hook-handler-execution. /sig docs /kind support
BTW we'd welcome a rewording that has the same meaning but that is easier for people to understand.
The existing text is correct but clearly at least one contributor did not understand it first go.
/remove-kind support
I think there's something we can fix here.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
/triage accepted
For contributors picking up this issue, please note the following:
/help
@divya-mohan0209: This request has been marked as needing help from a contributor.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
/assign
This paragraph is a bit confusing -
In first line, call is said to be
synchronous
. In second lineasynchronously