Use Fabric8 Kubernetes client in Kubernetes based integration tests #10545
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
Signed-off-by: Jakub Scholz <[email protected]>
see-quick
approved these changes
Sep 6, 2024
kornys
approved these changes
Sep 6, 2024
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.
Type of change
Description
Some of our integration tests that use Kubernetes currently use a strange mixture of the Fabric8 Kubernetes client and the Kubernetes / OpenShfit command line tools. That makes it hard to read. It also means that users need to have the command line utilities installed.
This PR updates the tests in the
api,operator-commonandcluster-operatormodules to rely only on the Fabric8 Kubernetes client. This should simplify them, make them easier to run and to maintain.Checklist