-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabling IPv6 for loadbalancers #191
Comments
Hi @fhofherr , I'm not sure if this fix actually solved the issue. I'm using the latest version of CCM and I can still see these error messages in the external-dns POD logs:
I'm using these kustomizations/annotations on the ingress controller service:
I also tried it with As @deyaeddin suggested I also rolled back to 1.8.1 and now external-dns works like a charm:
|
@janosmiko Here are my annotations, I'm using bitnami helm chart. Also, you might need to make sure you are on image: hetznercloud/hcloud-cloud-controller-manager:v1.10.0 in your Deployment. |
Hello,
Is there an option "annotation/flag" to disable IPv6 Support ?
I have upgraded CCM to v1.9.1 but the external-dns erroring to : the target A is not a valid record. As there is an open issue with external-dns regarding IPv6 support kubernetes-sigs/external-dns/issues/2044
I understand the feature was re-enabled #137 , but the ingress-nginx-controller is always publishing both IPv4 and IPv6 even with ConfigMap -> disable-ipv6-dns: "true"
The only workaround I found is to go back to v1.8.1 where IPv6 is completely not supported.
The text was updated successfully, but these errors were encountered: