Kubelet limit of Parallel Image Pulls

[ruiwen-zhao]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add a node-level limit to kubelet to limit the number of parallel image pulls
• Kubernetes Enhancement Proposal: https://hackmd.io/@zetEkgqtRbOBy8fi6e0dQg/H1cdueuPo/
• Discussion Link:
• Primary contact (assignee): @pacoxu @ruiwen-zhao
• Responsible SIGs: SIG Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3673: Kubelet limit of Parallel Image Pulls #3713
  • Code (k/k) update PR(s):
    • Add MaxParallelImagePulls support kubernetes#115220
  • Docs (k/website) update PR(s):
    • Document update for MaxParallelImagePulls website#39732

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

[ruiwen-zhao]

/sig node

[pacoxu]

Some intial ideas can be found in https://docs.google.com/document/d/1MMZlKSxkDBDz0kEn9JGm848_IJgydJqXWz5t9D3Ev8I/edit# and kubernetes/kubernetes#112242 kubernetes/kubernetes#112044

[wojtek-t]

/lead opted-in
/milestone v1.27

[wojtek-t]

/label lead-opted-in

[marosset]

Hello @pacoxu & @ruiwen-zhao 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for v1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this enhancement, it looks like #3713 will address most of these requirements.
Please be sure to also:

• Update the status to implemnetable in the kep.yaml (when ready)

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well.
Thank you!

[ruiwen-zhao]

Hello @pacoxu & @ruiwen-zhao 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for v1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this enhancement, it looks like #3713 will address most of these requirements. Please be sure to also:

• Update the status to implemnetable in the kep.yaml (when ready)

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

Updated the KEP PR #3713 to change the status to implemnetable. Once it is merged then all of the requirements will be addressed.

[marosset]

Thanks @ruiwen-zhao - this enhancement is ready to be tracked for v1.27

[pacoxu]

/assign @pacoxu @ruiwen-zhao

[ruiwen-zhao]

Draft document update: kubernetes/website#39732

[mickeyboxell]

Hi @ruiwen-zhao @pacoxu 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

[ruiwen-zhao]

Hi @ruiwen-zhao @pacoxu 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

Is kubernetes/website#39732 sufficient for now?

[marosset]

Hi @ruiwen-zhao @pacoxu 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

Please let me know if there are any other PRs in k/k I should be tracking for this KEP.
I see the following PR was closed (kubernetes/kubernetes#112242) - Is it going to be replaced with another PR?

As always, we are here to help should questions come up. Thanks!

[ruiwen-zhao]

Hi @marosset

The PR is kubernetes/kubernetes#115220, which has been merged already. Thanks!