Enforcing HTTPS on mirrors.jenkins.io + consolidating to get.jenkins.io

[Damien Duportal]

Hello there!

Reminder that we’re going to change the DNS record of `mirrors.jenkins.io` to `get.jenkins.io` in the upcoming hour, enforcing HTTPS.

Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/

Cheers,

For the infra team,

Damien DUPORTAL

[FredG]

Hi,

Do I assume correctly that this also affects the availability of ùpdates.jenkins.io`?

I'm having issues connecting to it (e.g. while trying to access the update center).

Regards,

Fred

[Damien Duportal]

Hello !

As per https://github.com/jenkins-infra/helpdesk/issues/2888#issuecomment-1131453254 and https://status.jenkins.io/issues/2022-05-19-outage-updates/,

we suffered from a side effect of this change: the DNS record "updates.jenkins.io" was a CNAME to mirrors.jenkins.io.

As a consequence, requests to updates.jenkins.io were sent to the Kubernetes cluster (instead of the VM serving the service updates.jenkins.io), leading to either HTTPS issues or HTTP/404 errors.

We fixed the DNS updates.jenkins.io (back to the VM) around 09:00am UTC but since the TTL was 1 hour, then you might see issues until 10:00am UTC (or until your DNS uncache the record).

Sorry for the inconvenience

[Damien Duportal]

Hello FredG,

our messages crossed, but yes, the errors on updates.jenkins.io are an un planned side effect of this change.

We try our best to keep status.jenkins.io up to date (sometime we fail ;) ) but it has the informations.

updates.jenkins.io should be back for you now: can you confirm?

Le jeudi 19 mai 2022 à 11:59:59 UTC+2, FredG a écrit :

[FredG]

Thanks Damien for the confirmation. I'm glad it's not "just me". :)

I can confirm that I can reach updates.jenkins.io again!

Regards,

Fred