You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead, let K8s create the Endpoints (Endpointslices) per Deployments.
For headless services, this requires adjusting tests to account for dynamically assigned IPs.
This further complicates testing ipv6 and dual stack cases.
For now, just fall back to testing ipv4, and leave ipv6 and dual stack tests to be handled later.
This may be an opportunity to re-implement the integrations tests entirely (e.g. moving away from circle ci) - perhaps moving them into coredns/coredns (which would greatly facilitate coordinating test and function changes).
The text was updated successfully, but these errors were encountered:
Instead, let K8s create the Endpoints (Endpointslices) per Deployments.
For headless services, this requires adjusting tests to account for dynamically assigned IPs.
This further complicates testing ipv6 and dual stack cases.
For now, just fall back to testing ipv4, and leave ipv6 and dual stack tests to be handled later.
This may be an opportunity to re-implement the integrations tests entirely (e.g. moving away from circle ci) - perhaps moving them into coredns/coredns (which would greatly facilitate coordinating test and function changes).
The text was updated successfully, but these errors were encountered: