Closed uablrek closed 1 year ago
According to the proposal (Endpoints (not EndpointSlice) addresses will match the first address family allocated to the Service (eg. An IPv6 Service IP will only have IPv6 Endpoints)
) and the implementation there should only be one endpoint.
What kind of issue is this?
/kind bug
Expected behaviour
For a service with
ipFamilyPolicy: RequireDualStack
endpoints of both families should be sent to the backend (always)Actual behaviour
I only get endpoints from one family. Which one, ipv4 or ipv6, seems a bit random.
I understand that this is a fundamental feature, without it dual-stack can't work, and all backends would fail. However, I suspect that the
to-api
may be the culprit. Or I have missed some updated configuration (I have been away from kpng for a while)Steps to reproduce the problem
Use the setup from the blog post. Use the service as-is and start 2 PODs with the correct selector. I use a
Deployment
with "replicas: 2", but that shouldn't be important.Output from
kpng-json | jq
:Only IPv4 endpoints are provided. But endpoins-slices for both families exist: