chore(deps): bump github.com/kong/kubernetes-telemetry from 0.0.3 to 0.0.4 #3977
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
programmer04
added
area/tests
dependencies
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #3977 +/- ##
=====================================
Coverage 58.8% 58.8%
=====================================
Files 139 139
Lines 16115 16115
=====================================
Hits 9477 9477
Misses 5991 5991
Partials 647 647 ☔ View full report in Codecov by Sentry. |
pmalek
approved these changes
May 9, 2023
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:
This PR bumps
github.com/kong/kubernetes-telemetryfrom0.0.3to0.0.4. Unit testTestCreateManageris adjusted, because telemetry pkg no longer uses oldCoreV1EndpointsAPI thus in mockDiscoveryV1EndpointSlicesAPI has to be used.Which issue this PR fixes:
It's a part of #3916
Special notes for your reviewer:
Surpasses #3973
PR Readiness Checklist:
Complete these before marking the PR as
ready to review:CHANGELOG.mdrelease notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR