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

Disallowing LifeCycle hooks for user container #687

Closed
tcnghia opened this issue Apr 18, 2018 · 2 comments
Closed

Disallowing LifeCycle hooks for user container #687

tcnghia opened this issue Apr 18, 2018 · 2 comments
Assignees
Labels
area/API API objects and controllers kind/feature Well-understood/specified features, ready for coding.

Comments

@tcnghia
Copy link
Contributor

tcnghia commented Apr 18, 2018

/area API
/kind dev
/assign @tcnghia

Expected Behavior

We are going to automatically specifying LifeCycle hooks for users in order to ensure a smooth autoscaling experience. It will be more complicated if users are also allowed to specify their LifeCycle hooks. We may want to disallow user LifeCycle hooks in order to keep a simple/easy user experience. If later they have use cases that need it we can consider adding back the support easily -- it won't be as easy the other direction.

Actual Behavior

LifeCycle hooks are allowed today.

@google-prow-robot google-prow-robot added area/API API objects and controllers kind/feature Well-understood/specified features, ready for coding. labels Apr 18, 2018
@tcnghia tcnghia removed their assignment Apr 18, 2018
@bsnchan
Copy link
Contributor

bsnchan commented Jun 21, 2018

/assign @tanzeeb @bsnchan

@joshua-smith4
Copy link

@tcnghia Having disabled lifecycle hooks, does knative serving expose some other API that allows pods to perform cleanup before being terminated?

ReToCode pushed a commit to ReToCode/serving that referenced this issue Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/API API objects and controllers kind/feature Well-understood/specified features, ready for coding.
Projects
None yet
Development

No branches or pull requests

5 participants