Skip to content
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

Closed
deyaeddin opened this issue May 2, 2021 · 2 comments · Fixed by #194
Closed

Disabling IPv6 for loadbalancers #191

deyaeddin opened this issue May 2, 2021 · 2 comments · Fixed by #194
Assignees

Comments

@deyaeddin
Copy link

deyaeddin commented May 2, 2021

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.

@fhofherr fhofherr self-assigned this May 5, 2021
fhofherr added a commit that referenced this issue May 5, 2021
Enabling IPv6 by default in #137 broke clusters using external-dns. This
commit adds an option to disable IPv6 by setting the

    load-balancer.hetzner.cloud/ipv6-disabled

annotation to false.

Closes #191
@fhofherr fhofherr pinned this issue May 5, 2021
fhofherr added a commit that referenced this issue May 6, 2021
Enabling IPv6 by default in #137 broke clusters using external-dns. This
commit adds an option to disable IPv6 by setting the

    load-balancer.hetzner.cloud/ipv6-disabled

annotation to true.

Closes #191
fhofherr added a commit that referenced this issue May 6, 2021
Enabling IPv6 by default in #137 broke clusters using external-dns. This
commit adds an option to disable IPv6 by setting the

    load-balancer.hetzner.cloud/ipv6-disabled

annotation to true.

Closes #191
@janosmiko
Copy link

janosmiko commented Jun 8, 2021

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:

me="2021-06-08T13:46:41Z" level=info msg="Desired change: CREATE domain.example.com A [Id: /hostedzone/XYZ123]"
time="2021-06-08T13:46:41Z" level=info msg="Desired change: CREATE domain.example.com TXT [Id: /hostedzone/XYZ123]"
time="2021-06-08T13:46:41Z" level=error msg="Failure in zone example.com. [Id: /hostedzone/XYZ123]"
time="2021-06-08T13:46:41Z" level=error msg="InvalidChangeBatch: [Invalid Resource Record: 'FATAL problem: ARRDATAIllegalIPv4Address (Value is not a valid IPv4 address) encountered with '2a01:4f8:1c1d:11c::1'']\n\tstatus code: 400, request id: 2c1833a2-7246-429e-b8eb-32cf712d206f"
time="2021-06-08T13:46:41Z" level=error msg="failed to submit all changes for the following zones: [/hostedzone/XYZ123]"

I'm using these kustomizations/annotations on the ingress controller service:

kind: Service
apiVersion: v1
metadata:
  name: ingress-nginx-controller
  annotations:
    externalTrafficPolicy: Local
    load-balancer.hetzner.cloud/location: nbg1
    load-balancer.hetzner.cloud/ipv6-disabled: "true"

I also tried it with true without the quotes, that didn't help either.

As @deyaeddin suggested I also rolled back to 1.8.1 and now external-dns works like a charm:

time="2021-06-08T13:54:45Z" level=info msg="2 record(s) in zone example.com. [Id: /hostedzone/XYZ123] were successfully updated"

@deyaeddin
Copy link
Author

@janosmiko
it works fine with me, maybe you need to double-check the quote "I would try a single quote in your case" .

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants