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

Updates the ttl-to-finished KEP to graduate the feature to Beta. #2246

Merged
merged 1 commit into from
Jan 19, 2021

Conversation

ahg-g
Copy link
Member

@ahg-g ahg-g commented Jan 8, 2021

Enhancement issue: #592

@ahg-g ahg-g requested review from janetkuo and wojtek-t January 8, 2021 21:21
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 8, 2021
@k8s-ci-robot k8s-ci-robot added the sig/apps Categorizes an issue or PR as relevant to SIG Apps. label Jan 8, 2021
@ahg-g
Copy link
Member Author

ahg-g commented Jan 8, 2021

@janetkuo should I move the "Finished Pods" section to a separate "Future Work" section?

@ahg-g ahg-g force-pushed the ahg-ttl branch 2 times, most recently from 745d0dd to 8ae83c7 Compare January 8, 2021 21:55
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/kep.yaml Outdated Show resolved Hide resolved
@wojtek-t wojtek-t self-assigned this Jan 11, 2021
@ahg-g ahg-g force-pushed the ahg-ttl branch 4 times, most recently from 3ee19b3 to 2627e6f Compare January 11, 2021 19:59
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/README.md Show resolved Hide resolved
@ahg-g ahg-g force-pushed the ahg-ttl branch 2 times, most recently from 72c9ab2 to 9581dd7 Compare January 13, 2021 14:49
keps/sig-apps/592-ttl-after-finish/README.md Outdated Show resolved Hide resolved
Unexpected restarts of kube-controller-manager

* **Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?**
Manually tested.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any findings?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, sorry, I thought I would be doing that before submitting the flag flip PR, I will do the test today.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had some issues with gce-enforcer (deleting firewall rules from my k8s on gce cluster), will try again tomorrow.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done, works as expected.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks - can you just added to the doc that non issues found?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

keps/sig-apps/592-ttl-after-finish/README.md Show resolved Hide resolved
Copy link
Member

@janetkuo janetkuo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I'll let @wojtek-t do the PRR review.

Unexpected restarts of kube-controller-manager

* **Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?**
Manually tested.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks - can you just added to the doc that non issues found?

* **How can a rollout fail? Can it impact already running workloads?**
It shouldn't impact already running workloads. This is an opt-in feature since users need to
explicitly set the TTLSecondsAfterFinished parameter in the job spec, which is silently dropped
by the api-server if the feature is disabled.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The field isn't dropped, right?
We're preserving the fields if they were set.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm - which isn't really a pattern we want to have. We generally want to avoid clearing explicitly set fields, e.g. in:
https://github.com/kubernetes/kubernetes/blob/d72c056260e771e8cd01220203582de0c0015786/pkg/api/pod/util.go#L450

@liggitt - FYI

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an existing behavior, do we want to change it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we want - though please reach out to @liggitt (or other API approver) for final confirmation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current behavior looks correct.. if the feature is disabled, we only preserve the field if it was already set in the persisted object, and clear it otherwise. That

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

keps/sig-apps/592-ttl-after-finish/README.md Show resolved Hide resolved
Copy link
Member

@wojtek-t wojtek-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with it modulo one minor nit and the open comment about dropping field - please resolve this one with API approvers.

You also need sig-apps approval.

* **How can a rollout fail? Can it impact already running workloads?**
It shouldn't impact already running workloads. This is an opt-in feature since users need to
explicitly set the TTLSecondsAfterFinished parameter in the job spec, which is silently dropped
by the api-server if the feature is disabled.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we want - though please reach out to @liggitt (or other API approver) for final confirmation.

keps/sig-apps/592-ttl-after-finish/README.md Show resolved Hide resolved
keps/sig-apps/592-ttl-after-finish/kep.yaml Show resolved Hide resolved
@wojtek-t
Copy link
Member

You also need sig-apps approval.

Actually - I see Janet already approved. So I will just wait for the "drop fields" discussion resolution and will approve.

@wojtek-t
Copy link
Member

LGTM

@ahg-g - please squash commits and I will approve

@ahg-g
Copy link
Member Author

ahg-g commented Jan 19, 2021

LGTM

@ahg-g - please squash commits and I will approve

thanks for the review, done!

promoted to beta after we finalize the decision for whether to generalize it or
not, and when it satisfies users' need for cleaning up finished resource
objects, without regressions.
- The feature implemented for Job, as future work, it can be extended to Pods and perhaps custom resources, but that should happen under separate feature flags.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your rebase didn't work - it seems you removed all the further commits....

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:(

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ops, forgot to git add . :) should be fixed now

@wojtek-t
Copy link
Member

Thanks!

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 19, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, janetkuo, wojtek-t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 19, 2021
@k8s-ci-robot k8s-ci-robot merged commit 70d927d into kubernetes:master Jan 19, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jan 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/apps Categorizes an issue or PR as relevant to SIG Apps. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants