-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Hook initContainers into lifecycle #45931
Comments
There's already lifecycle hook, is not enough? https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/ |
@kubernetes/sig-apps-feature-requests another request that is satisfied by hooks (#14512) / auto-pausing (#11505). |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/remove-lifecycle rotten |
Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
Kubernetes version (use
kubectl version
):Environment:
minikube
xhyve
macosx
uname -a
):Darwin ML-VSITZ-OSX-SF 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
Feature:
initContainers
feature works great for use cases when the initialization happens on the volumes. But oftentimes this initialization have to happen in the service itself, e.g: inject a datasource in grafana before grafana is considered ready: pre-ready.initContainers
feature doesn't seem o allow the container to be hooked to an specific moment of the lifecycle.initContainers
feature should allow the container to be hooked to an specific moment of the lifecycle.The text was updated successfully, but these errors were encountered: