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
Description:
I have recently stood up a k8s cluster with calico CNI and dual stack support. To my understanding, I need to explicitly specify IP family DualStack in a custom EnvoyProxy resource definition and link that to a gateway in order to get IPv6 support. After configuring this with a dedicated gateway, the gateway service is created with ipFamily: SingleStack and it pulls only an IPv4 address. If I use EnvoyProxy.spec.provider.kubernetes.patch to explicitly patch in ipFamilyPolicy: RequireDualStack the gateway service is granted an IPv6 address (from my metallb pool) but never passes readiness checks.
I'm looking for any direction I can get to debug this problem. I've tried helm chart v1.2.3, v1.2.4, and v0.0.0-latest as of this posting.
I have tested this out against the authentik helm chart. I have manually patched the created service to PreferDualStack and have confirmed it has a cluster IPv6 address (though I don't know if this is required for EG to route to it).
The gateway configuration below functions correctly as written over IPv4.
Description:
I have recently stood up a k8s cluster with calico CNI and dual stack support. To my understanding, I need to explicitly specify IP family
DualStack
in a customEnvoyProxy
resource definition and link that to a gateway in order to get IPv6 support. After configuring this with a dedicated gateway, the gateway service is created withipFamily: SingleStack
and it pulls only an IPv4 address. If I useEnvoyProxy.spec.provider.kubernetes.patch
to explicitly patch inipFamilyPolicy: RequireDualStack
the gateway service is granted an IPv6 address (from my metallb pool) but never passes readiness checks.I'm looking for any direction I can get to debug this problem. I've tried helm chart v1.2.3, v1.2.4, and v0.0.0-latest as of this posting.
I have tested this out against the authentik helm chart. I have manually patched the created service to
PreferDualStack
and have confirmed it has a cluster IPv6 address (though I don't know if this is required for EG to route to it).The gateway configuration below functions correctly as written over IPv4.
Repro steps:
Environment:
EG helm chart v1.2.3, v1.2.4, v0.0.0-latest
Logs:
Please let me know which logs I need to grab, I am not quite sure what is helpful.
The text was updated successfully, but these errors were encountered: