Skip to content

Commit

Permalink
Merge pull request #2841 from sahilvv/ttl_ga
Browse files Browse the repository at this point in the history
KEP-592: Graduate TTL after finish to stable
  • Loading branch information
k8s-ci-robot authored Aug 30, 2021
2 parents 43d81d8 + ee3a716 commit 97da0f7
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 3 deletions.
2 changes: 2 additions & 0 deletions keps/prod-readiness/sig-apps/592.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
kep-number: 592
beta:
approver: "@wojtek-t"
stable:
approver: "@wojtek-t"
5 changes: 4 additions & 1 deletion keps/sig-apps/592-ttl-after-finish/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,7 @@ Mitigations:

### Beta -> GA

- Make a decision on wehther or not the feature should be extended to pods
- TTL controller will be GA'ed without handling pods. The ability to extend TTL controller to work with pods can be introduced via a feature gate so that we can collect feedback and improve.
- Enabled in Beta for at least two releases without complaints

[umbrella issues]: https://github.com/kubernetes/kubernetes/issues/42752
Expand Down Expand Up @@ -427,3 +427,6 @@ When a Pod is created or updated:
- indicate that the feature will be graduated for Jobs, and that Pods will be done as future work under a separate flag
- add production readiness questionnaire
- mark the feature for Beta graduation for jobs.
- 2021-07-27: KEP updated to
- indicate that the feature will be graduated to stable for Jobs
- Pods will be done as future work if the need arises
5 changes: 3 additions & 2 deletions keps/sig-apps/592-ttl-after-finish/kep.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ kep-number: 592
authors:
- "@janetkuo"
- "@ahg-g"
- "@sahilvv"
owning-sig: sig-apps
participating-sigs:
- sig-api-machinery
Expand All @@ -23,12 +24,12 @@ superseded-by:
- n/a

# The target maturity stage in the current dev cycle for this KEP.
stage: beta
stage: stable

# The most recent milestone for which work toward delivery of this KEP has been
# done. This can be the current (upcoming) milestone, if it is being actively
# worked on.
latest-milestone: "v1.21"
latest-milestone: "v1.23"

# The milestone at which this feature was, or is targeted to be, at each stage.
milestone:
Expand Down

0 comments on commit 97da0f7

Please sign in to comment.