update external-resizer #631
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d-honeybadger
force-pushed
the
dkomsa/resizer-debug
branch
from
8f005fd to
1956cd4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There was an issue with external-resizer v1.13 failing the
Dynamic PV (default fs)(allowExpansion)test from upstream k8s suite.The bug was actually in the k8s e2e tests: kubernetes/kubernetes#129085
The upstream fix was merged and backported to k8s 1.30 - 1.32, so here I'm updating the e2e test binaries and removing 1.29 version since a) the fix wasn't backported to 1.29 and b) it's already removed in doks