Skip to content

Conversation

@jimmidyson
Copy link
Member

What problem does this PR solve?:

Default behaviour is retained, that is serialized image pulls actually configured by disabling forced serialized image pulls and setting max parallel image pulls to 1.

A value of zero means unlimited parallel image pulls.

Which issue(s) this PR fixes:
Fixes #

How Has This Been Tested?:

Special notes for your reviewer:

Copy link
Contributor

@yanhua121 yanhua121 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the default value of "maxParallelImagePullsPerNode" is set to 1, it is equivalent to enabling the serializeImagePulls. Do we want the default behavior of this to be the same as before (using serializeImagePulls), or set a reasonable default value (such as 5) to use parallel image pulling?

@yanhua121
Copy link
Contributor

If the default value of "maxParallelImagePullsPerNode" is set to 1, it is equivalent to enabling the serializeImagePulls. Do we want the default behavior of this to be the same as before (using serializeImagePulls), or set a reasonable default value (such as 5) to use parallel image pulling?

@jimmidyson replied:
i wanted to do that as a follow up conversation when we had more data on what that default should be
i also thought that NKP can be opinionated in the cluster templates we ship, whereas upstream CAREN can retain the default of 1

I think this is good.

@jimmidyson jimmidyson requested a review from dkoshkin September 17, 2025 08:45
@jimmidyson jimmidyson force-pushed the jimmi/parallel-image-pulls branch from 7bc8d8c to e026124 Compare September 17, 2025 09:21
@jimmidyson jimmidyson enabled auto-merge (squash) September 17, 2025 17:00
Default behaviour is retained, that is serialized image pulls
actually configured by disabling forced serialized image pulls
and setting max parallel image pulls to 1.

A value of zero means unlimited parallel image pulls.
@jimmidyson jimmidyson force-pushed the jimmi/parallel-image-pulls branch from af5ddf9 to 04440e8 Compare September 22, 2025 18:05
@dkoshkin dkoshkin enabled auto-merge (squash) September 22, 2025 19:20
@dkoshkin dkoshkin merged commit 64bc043 into main Sep 22, 2025
37 of 38 checks passed
@dkoshkin dkoshkin deleted the jimmi/parallel-image-pulls branch September 22, 2025 19:31
vijayaraghavanr31 pushed a commit that referenced this pull request Oct 8, 2025
**What problem does this PR solve?**:

Default behaviour is retained, that is serialized image pulls actually
configured by disabling forced serialized image pulls and setting max
parallel image pulls to 1.

A value of zero means unlimited parallel image pulls.


**Which issue(s) this PR fixes**:
Fixes #

**How Has This Been Tested?**:
<!--
Please describe the tests that you ran to verify your changes.
Provide output from the tests and any manual steps needed to replicate
the tests.
-->

**Special notes for your reviewer**:
<!--
Use this to provide any additional information to the reviewers.
This may include:
- Best way to review the PR.
- Where the author wants the most review attention on.
- etc.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants