tool(kuztomize): support version 5.4.2 and use it by default
#6144
Conversation
This file contains 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
vvagaytsev
force-pushed
the
tool/support-kuztomize-5
branch
from
2eb287c to
ffc1bfa
Compare
vvagaytsev
force-pushed
the
tool/support-kuztomize-5
branch
from
65468f4 to
3768594
Compare
Version 4 is still available over an explicit configuration.
vvagaytsev
force-pushed
the
tool/support-kuztomize-5
branch
from
3768594 to
d79e7bf
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.
What this PR does / why we need it:
Adds support for the latest available major version of
kustomize, and uses it by default in the code and Docker images.Which issue(s) this PR fixes:
Fixes #6128
Special notes for your reviewer:
Multi-version tool lookup still requires some hard-coding and manual lookup-key construction. So, a few files should be modified at once despite there is no obvious connection between them.
This is how it's done in nother multi-version tools. It would be nice to refactor that approach, but nice things are nice :)
The refactoring can be done for all tools in separate PR(s).