Using Endpoint Slices In K8S Logger instead of Endpoints API

A note for the community

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Use Cases

There are scalability issues with using endpoints API to get cluster information in kubernetes. It is discussed in more detail here. We faced this issue during our testing in large K8S cluster on GKE.

From the documentation, currently vector source kubernetes logs uses Pods Endpoints API .

Attempted Solutions

No response

Proposal

Proposal is to use K8S endpointslices API instead of endpoints API.

Endpoint API :
kubectl get --raw '/api/v1/namespaces/default/pods?watch=1'

Endpoint slices :
kubectl get --raw /apis/discovery.k8s.io/v1/watch/namespaces/default/endpointslices

References

No response

Version

0.22.0-distroless-libc

vectordotdev / vector