feat(k8s): Switch from CoreV1 Endpoints to DiscoveryV1 EndpointSlice #134
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.
EndpointSlice API is available as V1 since K8s 1.21. Let's do not rely on old Endpoint API in KTF.
It's been spotted during work on Kong/kubernetes-ingress-controller#3916. In KIC TestCreateManager depends on this package. In that test K8s objects have to be mocked, relying on obsolete
CoreV1 Endpoints
bykubernetes-telemetry
requires to use them in those mocks instead ofDiscoveryV1
API.