-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deps: bump kubernetes-client to 6.4.0 #1988
Conversation
Eclipse JKube CI ReportStarted new GH workflow run for #1988 (2023-01-24T06:38:31Z) ⚙️ JKube E2E Tests (3993480349)
|
74c61cd
to
867269e
Compare
Codecov Report
@@ Coverage Diff @@
## master #1988 +/- ##
=========================================
Coverage 54.11% 54.11%
+ Complexity 4050 4048 -2
=========================================
Files 480 480
Lines 21061 21061
Branches 2812 2812
=========================================
Hits 11397 11397
+ Misses 8499 8496 -3
- Partials 1165 1168 +3
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
867269e
to
85cf411
Compare
85cf411
to
4ee1006
Compare
4ee1006
to
e38da84
Compare
Signed-off-by: Marc Nuri <marc@marcnuri.com>
e38da84
to
7d0aafd
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
|
...ava/org/eclipse/jkube/kit/config/service/openshift/OpenshiftBuildServiceIntegrationTest.java
Show resolved
Hide resolved
@AfterEach | ||
void tearDown() { | ||
kubernetesClientMockedConstruction.close(); | ||
clusterConfiguration = ClusterConfiguration.builder() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it may be good to explain in the PR description why these changes were made and any reference to a kubernetes-client PR/issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes are just to improve the test and make use of the Kubernetes Mock Server provided by the client instead of relying on complex Mocks.
Why now? The Kubernetes Mock server as become more stable and performant over the last couple of years. Being able to test ClusterAccess
against a semi-real cluster is easier to maintain than relying on Mocks that need extra-maintenance. In this case, the Client is slowly moving to abstract away explicit KubernetesClient implementations and moving on to SPI provided and more generic ones instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is good for me, ideally in the description or in another PR
This should also fix #1540 |
Description
deps: bump kubernetes-client to 6.4.0
This PR includes changes to the
ClusterAccessTest
. The Kubernetes Mock server as become more stable and performant over the last couple of years. Being able to testClusterAccess
against a semi-real cluster is easier to maintain than relying on Mocks that need extra-maintenance. In this case, the Client is slowly moving to abstract away explicit KubernetesClient implementations and moving on to SPI provided and more generic ones instead.Type of change
test, version modification, documentation, etc.)
Checklist