feat: Support EndpointSlice in Kubernetes Provider

[arkodg]

• Reconcile relavant EndpointSlices associated with a Service that is referenced in a xRoute
• Add the EndpointSlices to the provider message

Relates to #1256

[codecov]

Codecov Report

Merging #1474 (c84c3cc) into main (22bd06b) will increase coverage by 0.18%.
The diff coverage is 49.18%.

@@            Coverage Diff             @@
##             main    #1474      +/-   ##
==========================================
+ Coverage   61.40%   61.58%   +0.18%     
==========================================
  Files          79       79              
  Lines       11459    11545      +86     
==========================================
+ Hits         7036     7110      +74     
- Misses       3962     3970       +8     
- Partials      461      465       +4     

Impacted Files	Coverage Δ
internal/gatewayapi/resource.go	51.51% <0.00%> (-1.61%)	⬇️
internal/gatewayapi/zz_generated.deepcopy.go	0.00% <0.00%> (ø)
internal/provider/kubernetes/controller.go	50.00% <48.00%> (+0.11%)	⬆️
internal/provider/kubernetes/predicates.go	56.33% <69.23%> (+0.56%)	⬆️

... and 4 files with indirect coverage changes

[zirain]

this's only part of #1256?

[arkodg]

this's only part of #1256?

yes, we need to take this data, and parse it in gateway api library which I plan on doing in a follow up PR

[zirain]

this's only part of #1256?

yes, we need to take this data, and parse it in gateway api library which I plan on doing in a follow up PR

what about endpoint, I know it will EOL soon, but in real world people always running old version kubernetes.

[arkodg]

this's only part of #1256?

yes, we need to take this data, and parse it in gateway api library which I plan on doing in a follow up PR

what about endpoint, I know it will EOL soon, but in real world people always running old version kubernetes.

currently we only support last 3 k8s versions
https://gateway.envoyproxy.io/v0.4.0/intro/compatibility.html#compatibility-matrix
by the time we GA, my guess is most users will be using k8s versions with endpointslice enabled

[zirain]

this's only part of #1256?

yes, we need to take this data, and parse it in gateway api library which I plan on doing in a follow up PR

what about endpoint, I know it will EOL soon, but in real world people always running old version kubernetes.

currently we only support last 3 k8s versions https://gateway.envoyproxy.io/v0.4.0/intro/compatibility.html#compatibility-matrix by the time we GA, my guess is most users will be using k8s versions with endpointslice enabled

I don't think that's the real world.

[arkodg]

this's only part of #1256?

yes, we need to take this data, and parse it in gateway api library which I plan on doing in a follow up PR

what about endpoint, I know it will EOL soon, but in real world people always running old version kubernetes.

currently we only support last 3 k8s versions https://gateway.envoyproxy.io/v0.4.0/intro/compatibility.html#compatibility-matrix by the time we GA, my guess is most users will be using k8s versions with endpointslice enabled

I don't think that's the real world.

users can always revert to the ClusterIP LB policy #1477