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’ll 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 kubernetes/kubernetes#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

Hello @wojtek-t 👋, 1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. This enhancement is targeting stable for 1.24 and it's a deprecation enhancement, are these correct?

Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release
  • Looks like the kep.yaml need updating to reflect current stage.
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.
  • Could you please confirm if this enhancement require a PRR approval?

The status of this enhancement is track as at risk. Please update this issue description with appropriate stages as well. Thank you!

@Priyankasaggu11929 - the PR to update the KEP is already out-for-review: #3118 (this should address the remaining bits from your above list).

Thanks @wojtek-t for the update! 🙂

@Priyankasaggu11929 - that PR was just approved. Let me know if there is anything else missing for the feature freeze here.

@wojtek-t, thanks for the update. With the KEP PR merged, this enhancement is ready to go for the enhancements freeze. 🙂

Hi @wojtek-t 👋🏻 1.24 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.

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

Thanks!

@mehabhalodiya - kubernetes/website#31756 is already opened for review

Hello @wojtek-t 👋

With 1.24 Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, I'm just checking in once more.

• All PRs to the Kubernetes repo that are related to your enhancement are merged by the code freeze deadline.
  • Update selflink doc kubernetes#108163
  • Deprecate SelfLink and introduce feature gate to disable its propagation kubernetes#80978
  • Avoid deep-copying object when possible on kube-apiserver watch path kubernetes#108252
• Have a documentation placeholder PR open by Thursday, March 31, 2022.
  • Graduate SelfLink deprecation to GA website#31756

With all the above check-boxes completed, this enhancement is all good for the upcoming 1.24 code freeze. 🚀 For note, the status of this enhancement is marked as tracked.

Kindly Please let me know if I'm missing any PRs other than the ones I linked above.

Also please link all the milestone PRs in the above issue description (for tracking purposes). Thank you so much!

@Priyankasaggu11929 - the above is correct - everything we need merged is merged

Hello @wojtek-t 👋, 1.25 Enhancements team here.

Since this feature has been fully deprecated now in K8s version 1.24.

Please update the kep.yaml file's status to implemented and close this issue.

This would help accurate tracking in the v1.25 cycle. Thank you so much! 🙂