Enhancements: Deprecate and remove SelfLink

Created on 23 Jul 2019  路  27Comments  路  Source: kubernetes/enhancements

Enhancement Description

  • One-line enhancement description (can be used as a release note): Deprecate and remove SelfLink fields
  • Kubernetes Enhancement Proposal: KEP
  • Primary contact (assignee): wojtek-t
  • Responsible SIGs: sig-apimachinery, sig-scalability
  • Enhancement target (which target equals to which milestone):

    • Alpha release target (1.16)

    • Beta release target (1.20)

    • Stable release target (1.21)

_Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement_

siapi-machinery siscalability stagbeta trackeyes

Most helpful comment

As mentioned above - we're code complete already.

All 27 comments

Hey @wojtek-t

I'm one of the v1.16 docs shadows.
Does this enhancement (or the work planned for v1.16) require any new docs (or modifications to existing docs)? If not, can you please update the 1.16 Enhancement Tracker Sheet (or let me know and I鈥檒l do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.16) due by Friday, August 23rd, it can just be a placeholder PR at this time. Let me know if you have any questions!

It will require some updates in the existing doc - I will open a PR closer to the time.

@wojtek-t code freeze for 1.16 is on Thursday 8/29. Are there any outstanding k/k PRs that still need to be merged for this to go Alpha? Looks like https://github.com/kubernetes/kubernetes/pull/80978 is merged. Thanks for tagging that.

Yes - everything required is merged.

Hey there @wojtek-t -- 1.17 Enhancements lead here. I know the plan is to follow the deprecation policy and target the 1.20/1.21 release for future work, but I just wanted to confirm it for tracking purposes 馃憤

Thanks!

/milestone clear

Yes - next steps are planned for 1.20.

/milestone v1.20

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

Hey there @wojtek-t -- 1.18 Enhancements shadow here. Just wanted to double check that this is not slated for 1.18? The 1.20 milestone is still correct?

Yes - 1.20 is correct.

thanks @wojtek-t !

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

@wojtek-t I see that this enhancement has been scheduled for graduation in 1.20. Let us know if plans change.


The current release schedule is:

  • Monday, April 13: Week 1 - Release cycle begins
  • Tuesday, May 19: Week 6 - Enhancements Freeze
  • Thursday, June 25: Week 11 - Code Freeze
  • Thursday, July 9: Week 14 - Docs must be completed and reviewed
  • Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

No - we need to satisfy deprecation policy, so we need to wait to 1.20.

@wojtek-t Thank you for the confirmation. :slightly_smiling_face:

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

Hi @wojtek-t !

Enhancements Lead here, just confirming that this is still on for 1.20?

Thanks!
Kirsten

Yes - KEP has been updated with PRR and the PR is already merged.
So yes - we're going to Beta in 1.20.

Cool!! As a note I fixed the link to the KEP in the description. :+1:

Hi @wojtek-t,

1.20 Enhancement shadow here 馃憢

Since this Enhancement is scheduled to be in 1.20, please keep in mind these important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thank you!

Hello @wojtek-t , 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against the dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th.

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@reylejano-rxm - we don't need any documentation for it.

Hi @wojtek-t

Please keep in mind the important upcoming dates:

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

As mentioned above - we're code complete already.

Was this page helpful?
0 / 5 - 0 ratings