-
Bug
-
Resolution: Done-Errata
-
Blocker
-
None
-
Quality / Stability / Reliability
-
3
-
False
-
-
False
-
oadp-operator-bundle-container-1.5.0-82
-
ToDo
-
-
-
0
-
Very Likely
-
0
-
0
-
None
-
Unset
-
Unknown
-
None
Description of problem:
row 76
PostStart is normally used to configure the container, set up dependencies, and record the new creation. You could use this event to check that a required API is available before the container's main work begins. Kubernetes will not change the container's state to Running until the PostStart script has executed successfully. For details, see https://www.containiq.com/post/kubernetes-container-lifecycle-events-and-hooks and https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks. PostStart is used to configure container, set up dependencies, record new creation. It can also be used to check that a required API is available before the container's work begins.
https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/
- relates to
-
OADP-5187 Operator best practices #90: Ensure that the containers lifecycle preStop management feature is configured
-
- Closed
-
- links to
-
RHEA-2025:145537 OpenShift API for Data Protection (OADP) 1.5
- mentioned on