[Cherry-Pick] Use calico_pool_blocksize from cluster when existing (#10516) #10771
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The blockSize attribute from Calico IPPool resources cannot be changed once set 1. Consequently, we use the one currently defined when configuring the existing IPPool, avoiding upgrade errors by trying to change it.
In particular, this can be useful when calico_pool_blocksize default changes in kubespray, which would otherwise force users to add an explicit setting to their inventories.
What type of PR is this?
/kind bug
What this PR does / why we need it:
The blockSize attribute from Calico IPPool resources cannot be changed
once set 1. Consequently, we use the one currently defined when
configuring the existing IPPool, avoiding upgrade errors by trying to
change it.
Which issue(s) this PR fixes:
#9055 (comment)
Special notes for your reviewer:
this PR cherry-pick #10516 to release-2.21
Does this PR introduce a user-facing change?: