Fix e2e test module component versions #1032
Merged
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.
Description
Currently, the
tests/e2e
module introduced dependencies on k8s components from v0.27.2 instead of the v0.26.4 we have in the other modules of this repo.Beyond not being in line with the supported k8s versions, this introduced a problem visible in testing (
make test
) and importing certain packages (e.g. some of our own packages even from this repo likepkg/webhooks
):That turns out to be a common issue when upgrading to modules that depend on
client-go
>v0.27.0
and is described succinctly here and here.The gist of it is (remember we are currently in v0.26.4 in our other modules):
For this PR, I removed all the
require
stanzas that had onlyindirect
dependencies in them fromtests/e2e/go.mod
and then rango mod tidy
on thetests/e2e
module. Then I did ago mod tidy
on the root module, too.Additionally, I am upgrading the
koperator
andkoperator/api
dependencies to the latest non-dev releases (at the time of writing).Additionally, I am upgrading the patch version of
Terratest
because ... it's available and it didn't cause any other dependency changes.Type of Change
Checklist