Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/area blog |
|
Hello from the blog team. We recommend drafting in either HackMD or Google Docs; once you're happy with the text and your buddy / reviewer is happy too, you can switch back to Git / GitHub ready for it to merge in. |
|
Hi @esotsal 👋 v1.36 Communications team here, @kannon92 as author of #54548, I'd like you to be a writing buddy for @esotsal on this PR. Please:
|
|
/assign Happy too! @esotsal let me know when it's ready for review. |
Hi I am afraid we need to postpone this based on my comment here kubernetes/kubernetes#129719 (comment) |
|
@kannon92 , @chadmcrowell , @lmktfy thanks for your support, as per kubernetes/kubernetes#129719 (comment) we have decided it is best to postpone this KEP, aiming for v1.37 after having solved the blocking issue with CPU Manager checkpoint in a generic way as per kubernetes/kubernetes#129719 (comment). I have reopened the PR to use for v1.37 new alpha milestone for KEP-5554 kubernetes/enhancements#5965 , if you prefer to close this instead please let me know. |
Description
Placeholder Blog PR for KEP-5554
Issue
kubernetes/enhancements#5554