Add AAAA records, support installs IPv6 only environments

[BartjeD]

Per the title my use case is an IPv6 only environment.
I'm attempting to install Jenkins bare metal on a Debian 11 environment.

The first issue I run into is that the mirror is unreachable because it doesn't have an AAAA record.

I've considered using the Docker IPv6 infrastructure and LTS container instead.
But I really like the charm of simply using apt to update Jenkins and not having to use a container at all.

Given that countries like India are now IPv6 only, and that other countries are moving to IPv6 being a lot cheaper than having servers with IPv4 I'm wondering why the infrastructure of the world's most popular CI doesn't support this basic scenario (yet?) :D

Could these AAAA records be added?

And is my assumption correct that Jenkins will work on IPv6?
I'm assuming I will have to set it to prefer IPv6 over IPv4 as a Java dual stack environmental configuration.

Thanks in advance!
B

[dduportal]

Hi @BartjeD , thanks for raising the issue.

For any issue with Jenkins itself, please open an issue on community.jenkins.io where you'll benefit from the help of the community.

Regarding the Jenkins public infrastructure, I'm not sure to understand the issue?
We do not have AAAA DNS record for a reason: we do not have public IPv6 for providing the services.
I'm not aware of IPv4 not being usable when your infrastructure is using IPv6: do you have more information on that topic? It seems quite a breaking change of the internet (I don't say we should not use IPv6, but it has a "cost" so if need it has to be planned). ?

[BartjeD]

IPv6 isn't compatible with IPv4 by design.

You can use a NAT64 gateway to map to IPv4 but then you still need a machine with an IPv4. Which you don't have in a IPv6 only situation. Like mine.

This is what docker writes:
https://www.docker.com/blog/beta-ipv6-support-on-docker-hub-registry/

You can find more about it here,
https://www.zdnet.com/home-and-office/networking/five-ways-for-ipv6-and-ipv4-to-peacefully-co-exist/

[dduportal]

Thanks @BartjeD for the pointers.

For the team: we already got an (old) issue about IPv6: #62

[dduportal]

For information, in order to solve this issue, we are working on the underlying networks of our infrastructure as described in #2924.

We'll update this issue once fixed.

[BartjeD]

:) Outlook voor Android<https://aka.ms/AAb9ysg> downloaden

…

________________________________ From: Damien Duportal ***@***.***> Sent: Thursday, November 24, 2022 2:56:49 PM To: jenkins-infra/helpdesk ***@***.***> Cc: BartjeD ***@***.***>; Mention ***@***.***> Subject: Re: [jenkins-infra/helpdesk] Add AAAA records, support installs IPv6 only environments (Issue #3227) For information, in order to solve this issue, we are working on the underlying networks of our infrastructure as described in #2924<#2924>. We'll update this issue once fixed. — Reply to this email directly, view it on GitHub<#3227 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL4NXWPJ22XBEV2PWKUXOZLWJ5X2DANCNFSM6AAAAAAR3IRIUU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dduportal]

Hi @BartjeD , we just finished exposing https://get.jenkins.io through IPv6 in #3639 .

Other services might have to be exposed: do you have some examples that you are failing to use with IPv6?

We'll continue in this issue and close when all services will be reachable through both stacks.

[lemeurherve]

Since the addition of the dedicated IPv6 load balancer service for #3639 there is nothing more to do, every service hosted on publick8s cluster are accessible via IPv6 🎉

EDIT: I still had to create the two AAAA apex records for jenkins.io & jenkins-ci.org in jenkins-infra/azure-net#118