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

Pod expiration time #85752

Open
icy opened this issue Nov 29, 2019 · 5 comments

Comments

@icy
Copy link

@icy icy commented Nov 29, 2019

What would you like to be added:

Pod has new attribute "Expiration Time" after that the Pod would stop to receive any connections and exit gracefully and the deployment (or daemonset...) will launch another pod to replace it.

Why is this needed:

Because k8s is fun and having this feature is also fun

@icy icy added the kind/feature label Nov 29, 2019
@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

@k8s-ci-robot k8s-ci-robot commented Nov 29, 2019

@icy: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@liggitt

This comment has been minimized.

Copy link
Member

@liggitt liggitt commented Nov 29, 2019

The activeDeadlineSeconds allows bounding pod execution time

@icy

This comment has been minimized.

Copy link
Author

@icy icy commented Dec 2, 2019

@liggitt I think activeDeadlineSeconds is applied to Job and it's not available for deployment/daemonset.

@liggitt

This comment has been minimized.

Copy link
Member

@liggitt liggitt commented Dec 2, 2019

you're right:

		if template.Spec.ActiveDeadlineSeconds != nil {
			allErrs = append(allErrs, field.Forbidden(fldPath.Child("spec", "activeDeadlineSeconds"), "activeDeadlineSeconds in ReplicaSet is not Supported"))
		}
@liggitt

This comment has been minimized.

Copy link
Member

@liggitt liggitt commented Dec 2, 2019

/priority awaiting-more-evidence

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.