Hi @liggitt, as I believe you are aware we recently merged #1620 which adds the PRR questions to the KEP, as well as some additional metadata to the kep.yaml. Please update the KEP when you have a chance. Thanks!

Hi @liggitt - My name is Zachary, 1.19 Docs shadow. Is this enhancement work planned for 1.19 and does it require any new docs (or modifications to existing docs)? If not, can you please update the 1.19 Enhancement Tracker Sheet, or let me know, I can do it for you :)
If docs are required, just a friendly reminder that we are looking for a PR against k/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

I will update the KEP format as I have the opportunity to.

Yes, this is planned for 1.19. There will be some doc additions describing metrics for tracking deprecated API use.

Hi @liggitt - Just a reminder that docs placeholder PR against dev-1.19 is due by June 12th. Does this enhancement require any changes to docs? If so, can you update here with a link to the PR once you have it in place? If not, please update the same, so that the tracking sheet can be updated accordingly. Thanks!

opened placeholder at kubernetes/website#21581

Hi @liggitt !

To follow-up on the email sent to k-dev on Monday, I wanted to let you know that Code Freeze has been extended to Thursday, July 9th. You can see the revised schedule here: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.19
We expect all PRs to be merged by that time. Please let me know if you have any questions. 😄

Best,

Kirsten

Hi @liggitt 👋, is kubernetes/kubernetes#92329 the only implementation PR for this feature? If not, can you please link here all the other implementation PRs?

Thank you. 🙂

remaining implementation PRs:

• Add deprecated, deprecationWarning fields to CRDs kubernetes#92329
• Admission webhook warnings kubernetes#92667

@liggitt -- Thank you for the updates. 🙂

Hi @liggitt 👋, I saw that all the implementation PRs mentioned above have been merged. Can we consider the work complete for this milestone?

Thank you. 🙂

One last impl PR at kubernetes/kubernetes#92842

The doc PR is ready for review

Hi @liggitt

Will the above PR get merge by EOD today? Today is code freeze.

Thanks!

That depends on how the merge queue makes progress. It is reviewed and approved and in the milestone, so it will merge as the queue drains.

@liggitt I double checked and we have several fully approved, properly tagged, etc.. that are stuck in the merge pool. They will be considered making the deadline and we'll be following their progress closely.

Thanks for the update!

Kirsten

@liggitt kubernetes/kubernetes#92842 finally merged! I will update the enhancements tracking sheet to reflect this. Congrats!

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@fejta-bot: Closing this issue.

Hi @liggitt 👋 1.22 Enhancements Shadow here.

This enhancement is in good shape, some minor change requests in light of Enhancement Freeze on Thursday May 13th:

• Please up date your kep.yaml file with the latest template
• I was unable to find the PRR for this enhancements so it will be marked as PRR not approved

Thanks!

Hi @liggitt 👋 1.22 Enhancements shadow here.
I just wanted to double check to see if SIG-api-machinery will need to do anything for this enhancement and if so, are they OK with it?
Thanks!

#2719 open to update KEP with milestone and add PRR answers

I just wanted to double check to see if SIG-api-machinery will need to do anything for this enhancement and if so, are they OK with it?

The KEP/PRR work is complete and merged:

• GA 1693: warnings #2719

The implementation PRs are pending review:

• Add field-level warning plumbing and add pod spec warnings kubernetes#101688
• Graduate WarningHeader feature to GA kubernetes#100754

Heya @liggitt Docs release lead for 1.22 here, this KEP did not opt-in for docs changes for 1.22, however, and please correct me if i'm wrong, it seems that one of you PRs marks WarningHeaders as GA, this would mean that the feature gates table in the docs needs to reflect that change.
If that is true, could you or someone from the SIG open a PR against the k/website dev-1.22 branch to make this change?

thank you!

sure, kubernetes/website#28032

Hi @liggitt 🌞 1.22 enhancements shadow here.

In light of Code Freeze on July 8th, are k/k#101688 and k/k#100754 the only PRs for this enhancements?

Thank you!

yes

Hey @liggitt - Would you be able to open a PR on the KEP to change the stage to implemented? At that point we'll be able to close out the issue. :)

Thanks!

opened #2875