<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://status.jenkins.io/"/><title>Mirrors.jenkins.io on Jenkins Status Page</title><link>https://status.jenkins.io/affected/mirrors.jenkins.io/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2025-12-15T08:30:00+00:00</lastBuildDate><updated>2025-12-15T08:30:00+00:00</updated><atom:link href="https://status.jenkins.io/affected/mirrors.jenkins.io/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] [publick8s cluster] Azure publick8s Upgrade to Kubernetes 1.33.5</title><link>https://status.jenkins.io/issues/2025-12-15-maintenance-azure-publick8s-1-33/</link><pubDate>Mon, 15 Dec 2025 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-12-15-maintenance-azure-publick8s-1-33/</guid><category>2025-12-15T09:15:00-00:00</category><description>&lt;p&gt;[Final Message]
upgrade went well, no impact on production.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Monday 15 December 2025 at 08:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.33.5. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
upgrade went well, no impact on production.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Monday 15 December 2025 at 08:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.33.5. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;issue-redirect.jenkins.io&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3548729217"&gt;https://github.com/jenkins-infra/helpdesk/issues/4820#issuecomment-3548729217&lt;/a&gt;.&lt;/p&gt;</content></item><item><title>[Resolved] Azure cluster publick8s migrated to a new location and upgraded to Kubernetes 1.32</title><link>https://status.jenkins.io/issues/2025-09-25-azure-publick8s-1-32-adn-migration/</link><pubDate>Thu, 25 Sep 2025 11:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-09-25-azure-publick8s-1-32-adn-migration/</guid><category>2025-09-26T09:30:00-00:00</category><description>&lt;p&gt;[Final Message]
Outage finished on Friday 26 September 2025 at 09:35am UTC and post mortem published: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4813#issuecomment-3339518665"&gt;https://github.com/jenkins-infra/helpdesk/issues/4813#issuecomment-3339518665&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Update]
Friday 26 September 2025 at 09:35am UTC: ongoing production outage on the cluster (unexpected side effect of the migration): &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4813"&gt;https://github.com/jenkins-infra/helpdesk/issues/4813&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Update]
Migration was finished on Thursday 25 September 2025 at 03:30PM UTC. See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4617#issuecomment-3334826339"&gt;https://github.com/jenkins-infra/helpdesk/issues/4617#issuecomment-3334826339&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday 25 September 2025, starting at 11:30AM UTC, we&amp;rsquo;ll perform a migration + upgrade of the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to a new location and to Kubernetes 1.32.&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
Outage finished on Friday 26 September 2025 at 09:35am UTC and post mortem published: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4813#issuecomment-3339518665"&gt;https://github.com/jenkins-infra/helpdesk/issues/4813#issuecomment-3339518665&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Update]
Friday 26 September 2025 at 09:35am UTC: ongoing production outage on the cluster (unexpected side effect of the migration): &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4813"&gt;https://github.com/jenkins-infra/helpdesk/issues/4813&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Update]
Migration was finished on Thursday 25 September 2025 at 03:30PM UTC. See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4617#issuecomment-3334826339"&gt;https://github.com/jenkins-infra/helpdesk/issues/4617#issuecomment-3334826339&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday 25 September 2025, starting at 11:30AM UTC, we&amp;rsquo;ll perform a migration + upgrade of the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to a new location and to Kubernetes 1.32.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4617"&gt;https://github.com/jenkins-infra/helpdesk/issues/4617&lt;/a&gt;.&lt;/p&gt;</content></item><item><title>[Resolved] Enforced HTTPS for Update Center</title><link>https://status.jenkins.io/issues/2025-08-06-uc-enforce-https/</link><pubDate>Wed, 06 Aug 2025 07:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-08-06-uc-enforce-https/</guid><category>2025-08-06T09:30:00-00:00</category><description>&lt;p&gt;Wednesday 06 August 2025 at 07:00am UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will be upgraded to enforced HTTPS as described in &lt;a href="https://www.jenkins.io/blog/2025/08/04/update-center-enforce-https/"&gt;https://www.jenkins.io/blog/2025/08/04/update-center-enforce-https/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The operation should take from 5 to 30 minutes (depends on the Azure Cloud ability to spin up resources on demand).&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.
Eventually, some requests may time out during the deployment of the new settings.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4758"&gt;https://github.com/jenkins-infra/helpdesk/issues/4758&lt;/a&gt;.&lt;/p&gt;</description><content type="html">&lt;p&gt;Wednesday 06 August 2025 at 07:00am UTC, the service &lt;a href="https://updates.jenkins.io"&gt;https://updates.jenkins.io&lt;/a&gt; will be upgraded to enforced HTTPS as described in &lt;a href="https://www.jenkins.io/blog/2025/08/04/update-center-enforce-https/"&gt;https://www.jenkins.io/blog/2025/08/04/update-center-enforce-https/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The operation should take from 5 to 30 minutes (depends on the Azure Cloud ability to spin up resources on demand).&lt;/p&gt;
&lt;p&gt;All Jenkins users are impacted but should not see any functional change.
Eventually, some requests may time out during the deployment of the new settings.&lt;/p&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4758"&gt;https://github.com/jenkins-infra/helpdesk/issues/4758&lt;/a&gt;.&lt;/p&gt;</content></item><item><title>[Resolved] [publick8s cluster] Azure publick8s Upgrade to Kubernetes 1.31.6</title><link>https://status.jenkins.io/issues/2025-04-24-maintenance-azure-publick8s-1-31/</link><pubDate>Thu, 24 Apr 2025 07:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-04-24-maintenance-azure-publick8s-1-31/</guid><category>2025-04-24T8:20:00-00:00</category><description>&lt;p&gt;[Final Message]
upgrade went well, no impact on production.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday 24 April 2025, at 07:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.31.6. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;⚠️ Last Kubernetes upgrade (to 1.30) we saw an outage on update-center (updates.jenkins.io) for a few seconds !&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
upgrade went well, no impact on production.&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thursday 24 April 2025, at 07:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.31.6. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;⚠️ Last Kubernetes upgrade (to 1.30) we saw an outage on update-center (updates.jenkins.io) for a few seconds !&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4546#issuecomment-2674545933"&gt;https://github.com/jenkins-infra/helpdesk/issues/4546#issuecomment-2674545933&lt;/a&gt;.&lt;/p&gt;</content></item><item><title>[Resolved] [publick8s cluster] Azure publick8s Upgrade to Kubernetes 1.30.7</title><link>https://status.jenkins.io/issues/2025-02-19-maintenance-azure-publick8s-1-30/</link><pubDate>Thu, 20 Feb 2025 13:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2025-02-19-maintenance-azure-publick8s-1-30/</guid><category>2025-02-20T14:10:00-00:00</category><description>&lt;p&gt;[Final Message]
upgrade went well but we saw an outage on update center for about 2 to 3 mn
we will analyse further the logs to try to understand were it&amp;rsquo;s coming from&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thurday 20 February 2025, at 01:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.30.7. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
upgrade went well but we saw an outage on update center for about 2 to 3 mn
we will analyse further the logs to try to understand were it&amp;rsquo;s coming from&lt;/p&gt;
&lt;p&gt;[Initial Message]
Thurday 20 February 2025, at 01:30PM UTC, we&amp;rsquo;ll upgrade the AKS(Azure) cluster &lt;code&gt;publick8s&lt;/code&gt; to Kubernetes 1.30.7. It should take between 60 and 120 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2663553626"&gt;https://github.com/jenkins-infra/helpdesk/issues/4258#issuecomment-2663553626&lt;/a&gt;.&lt;/p&gt;</content></item><item><title>[Resolved] AKS cluster upgrade to 1.29.10 (patch)</title><link>https://status.jenkins.io/issues/2024-12-18-maintenance-aks-1.29.10/</link><pubDate>Wed, 18 Dec 2024 09:45:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-12-18-maintenance-aks-1.29.10/</guid><category>2024-12-18T14:00:00-00:00</category><description>&lt;p&gt;We&amp;rsquo;re performing AKS cluster upgrade from 1.29.7 to 1.29.10 the 18 December 2024, starting at 09:45 UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;</description><content type="html">&lt;p&gt;We&amp;rsquo;re performing AKS cluster upgrade from 1.29.7 to 1.29.10 the 18 December 2024, starting at 09:45 UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;</content></item><item><title>[Resolved] Update Azure AKS cluster `publick8s` to 1.29</title><link>https://status.jenkins.io/issues/2024-08-23-maintenance-az-publick8s-1-29/</link><pubDate>Fri, 23 Aug 2024 09:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-08-23-maintenance-az-publick8s-1-29/</guid><category>2024-08-23T09:40:00-00:00</category><description>&lt;p&gt;Friday 23 August at 07:30am UTC, the AKS cluster &lt;code&gt;publick8s&lt;/code&gt; will be upgraded to Kubernetes 1.29.7. It should take between 30 and 60 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;</description><content type="html">&lt;p&gt;Friday 23 August at 07:30am UTC, the AKS cluster &lt;code&gt;publick8s&lt;/code&gt; will be upgraded to Kubernetes 1.29.7. It should take between 30 and 60 min.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following services, with a downtime between 2 and 15 min (depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-in/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4161"&gt;https://github.com/jenkins-infra/helpdesk/issues/4161&lt;/a&gt;.&lt;/p&gt;</content></item><item><title>[Resolved] Update azure clusters publick8s Kubernetes version to 1.28</title><link>https://status.jenkins.io/issues/2024-07-03-maintenance-az-publick8s-1-28/</link><pubDate>Thu, 04 Jul 2024 06:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-07-03-maintenance-az-publick8s-1-28/</guid><category>2024-07-04T7:15:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 7:15am UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4144#issuecomment-2196274746"&gt;https://github.com/jenkins-infra/helpdesk/issues/4144#issuecomment-2196274746&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an publick8s AZ cluster upgrade from 1.27 to 1.28 tomorrow, 4th of July 2024, starting at 6:30 UTC (8h30 paris time, 12h00 IST).&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
The operation finished successfully at 7:15am UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/4144#issuecomment-2196274746"&gt;https://github.com/jenkins-infra/helpdesk/issues/4144#issuecomment-2196274746&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an publick8s AZ cluster upgrade from 1.27 to 1.28 tomorrow, 4th of July 2024, starting at 6:30 UTC (8h30 paris time, 12h00 IST).&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) due to public IP metadata changes and falco + Nginx upgrades:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;plugin-health.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content></item><item><title>[Resolved] Update azure clusters publick8s Kubernetes version to 1.27</title><link>https://status.jenkins.io/issues/2024-03-19-maintenance-az-publick8s-1-27/</link><pubDate>Tue, 19 Mar 2024 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-03-19-maintenance-az-publick8s-1-27/</guid><category>2024-03-19T9:35:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 9:35am UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3948#issuecomment-1991181964"&gt;https://github.com/jenkins-infra/helpdesk/issues/3948#issuecomment-1991181964&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an publick8s AZ cluster upgrade from 1.26 to 1.27 today 19th of Mars 2024, starting at 8:30 UTC (9h30 paris time).&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
The operation finished successfully at 9:35am UTC.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3948#issuecomment-1991181964"&gt;https://github.com/jenkins-infra/helpdesk/issues/3948#issuecomment-1991181964&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial message]
We&amp;rsquo;re doing an publick8s AZ cluster upgrade from 1.26 to 1.27 today 19th of Mars 2024, starting at 8:30 UTC (9h30 paris time).&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) due to public IP metadata changes and falco + Nginx upgrades:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content></item><item><title>[Resolved] get(mirrors).jenkins.io storage migration</title><link>https://status.jenkins.io/issues/2024-01-26-get.jenkins.io-migration/</link><pubDate>Fri, 26 Jan 2024 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-26-get.jenkins.io-migration/</guid><category>2024-01-26T12:15:00-00:00</category><description>&lt;p&gt;A maintenance on get.jenkins.io (mirrors.jenkins*) will be performed with a &lt;strong&gt;partial service disruption&lt;/strong&gt; the Friday 26 January 2024 starting at 12:00pm (noon time) UTC.&lt;/p&gt;
&lt;p&gt;The goal of this maintenance is to migrate the underlying storage to a new system in Azure.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3917"&gt;https://github.com/jenkins-infra/helpdesk/issues/3917&lt;/a&gt; for more details.&lt;/p&gt;</description><content type="html">&lt;p&gt;A maintenance on get.jenkins.io (mirrors.jenkins*) will be performed with a &lt;strong&gt;partial service disruption&lt;/strong&gt; the Friday 26 January 2024 starting at 12:00pm (noon time) UTC.&lt;/p&gt;
&lt;p&gt;The goal of this maintenance is to migrate the underlying storage to a new system in Azure.&lt;/p&gt;
&lt;p&gt;See &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3917"&gt;https://github.com/jenkins-infra/helpdesk/issues/3917&lt;/a&gt; for more details.&lt;/p&gt;</content></item><item><title>[Resolved] get.jenkins.io maintenance</title><link>https://status.jenkins.io/issues/2024-01-08-get-jenkins-io-maintenance/</link><pubDate>Mon, 08 Jan 2024 15:15:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2024-01-08-get-jenkins-io-maintenance/</guid><category>2024-01-09T12:00:00-00:00</category><description>&lt;p&gt;[Final Message]
THe migration is finally finished at noon UTC the 09th.
There were 2 downtimes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;2 min the 8th around 17:30 UTC (TLS errors) due to a missing ingress configuration&lt;/li&gt;
&lt;li&gt;5 min the 9th around 11:50 UTC (HTTP/500 errors) due to a race condition in helm chart deployments&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
Monday January 8 2024, starting at 15:15 UTC, we&amp;rsquo;ll proceed to a maintenance on the service &lt;code&gt;get.jenkins.io&lt;/code&gt; hosted in the &lt;code&gt;publick8s&lt;/code&gt; Azure Kubernetes cluster.&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
THe migration is finally finished at noon UTC the 09th.
There were 2 downtimes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;2 min the 8th around 17:30 UTC (TLS errors) due to a missing ingress configuration&lt;/li&gt;
&lt;li&gt;5 min the 9th around 11:50 UTC (HTTP/500 errors) due to a race condition in helm chart deployments&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;[Initial Message]
Monday January 8 2024, starting at 15:15 UTC, we&amp;rsquo;ll proceed to a maintenance on the service &lt;code&gt;get.jenkins.io&lt;/code&gt; hosted in the &lt;code&gt;publick8s&lt;/code&gt; Azure Kubernetes cluster.&lt;/p&gt;
&lt;p&gt;The following services will be slower to respond or even might be disrupted:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (Jenkins download redirection to mirrors)&lt;/li&gt;
&lt;li&gt;mirrors.jenkins-ci.org (Jenkins download redirection to mirrors)&lt;/li&gt;
&lt;li&gt;mirrors.jenkins.io (Jenkins download redirection to mirrors)&lt;/li&gt;
&lt;li&gt;fallback.get.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The goal is to change the helm chart use to deploy the service from the legacy &lt;code&gt;mirrorbits&lt;/code&gt; to the new &lt;code&gt;mirrorbits-parent&lt;/code&gt; to benefit from:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Apache running in &lt;code&gt;arm64&lt;/code&gt; Linux systems (cheaper)&lt;/li&gt;
&lt;li&gt;Readonly filesystem for shared data (safety)&lt;/li&gt;
&lt;li&gt;Same features as the current updates-jenkins-io service (maintenance and sustainability)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More details in: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3828"&gt;https://github.com/jenkins-infra/helpdesk/issues/3828&lt;/a&gt;&lt;/p&gt;</content></item><item><title>[Resolved] Update publick8s AKS cluster to Kubernetes 1.26</title><link>https://status.jenkins.io/issues/2023-11-09-maintenance-aks-1.26-publick8s/</link><pubDate>Thu, 09 Nov 2023 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-11-09-maintenance-aks-1.26-publick8s/</guid><category>2023-11-09T11:00:00-00:00</category><description>&lt;p&gt;[Final Message]
The operation finished successfully at 11:00am UTC.
The monitoring showed an outage of 6 minutes on the LDAP and 2 minutes on the incremental publisher.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1803566680"&gt;https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1803566680&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
The AKS cluster &lt;code&gt;publick8s&lt;/code&gt; will be upgraded from Kubernetes 1.25 to 1.26 the Thursday 09th of November 2023, starting at 08:30am UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final Message]
The operation finished successfully at 11:00am UTC.
The monitoring showed an outage of 6 minutes on the LDAP and 2 minutes on the incremental publisher.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1803566680"&gt;https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1803566680&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[Initial Message]
The AKS cluster &lt;code&gt;publick8s&lt;/code&gt; will be upgraded from Kubernetes 1.25 to 1.26 the Thursday 09th of November 2023, starting at 08:30am UTC.&lt;/p&gt;
&lt;p&gt;The expected impacts are:&lt;/p&gt;
&lt;p&gt;Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ldap.jenkins.io&lt;/li&gt;
&lt;li&gt;weekly.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;incrementals.jenkins.io&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;accounts.jenkins.io&lt;/li&gt;
&lt;li&gt;ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io&lt;/li&gt;
&lt;li&gt;issues.jenkins.io (JIRA)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Temporary disruptions (slow requests or outage of a few minutes) due to public IP metadata changes and falco + Nginx upgrades:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;get.jenkins.io (mirror redirector)&lt;/li&gt;
&lt;li&gt;javadoc.jenkins.io&lt;/li&gt;
&lt;li&gt;jenkins-wiki-exporter.jenkins.io&lt;/li&gt;
&lt;li&gt;plugins.jenkins.io&lt;/li&gt;
&lt;li&gt;repo.azure.jenkins.io&lt;/li&gt;
&lt;li&gt;reports.jenkins.io&lt;/li&gt;
&lt;li&gt;stories.jenkins.io&lt;/li&gt;
&lt;li&gt;uplink.jenkins.io&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.jenkins.io"&gt;www.jenkins.io&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content></item><item><title>[Resolved] arm64 migration of mirrorbits</title><link>https://status.jenkins.io/issues/2023-10-25-mirrorbits-arm64-migration/</link><pubDate>Wed, 25 Oct 2023 16:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-25-mirrorbits-arm64-migration/</guid><category>2023-10-25T17:00:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is postponed as we encountered issues with some binaries not built for arm64 architecture in our images, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Wednesday October 25 2023, starting at 16:00 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the mirrorbits service responsible for get.jenkins.io, fallback.get.jenkins.io, mirrors.jenkins.io and mirror.jenkins-ci.org.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of these services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is postponed as we encountered issues with some binaries not built for arm64 architecture in our images, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Wednesday October 25 2023, starting at 16:00 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the mirrorbits service responsible for get.jenkins.io, fallback.get.jenkins.io, mirrors.jenkins.io and mirror.jenkins-ci.org.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of these services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</content></item><item><title>[Resolved] arm64 migration of public nginx ingress on publick8s cluster</title><link>https://status.jenkins.io/issues/2023-10-19-publik8s-public-nginx-ingress-arm64-migration/</link><pubDate>Tue, 10 Oct 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-10-19-publik8s-public-nginx-ingress-arm64-migration/</guid><category>2023-10-10T12:15:00-00:00</category><description>&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is now finished, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Thursday October 19 2023, starting at 12:00 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the publick8s nginx ingress, hosting most of Jenkins Infrastructure public-facing services in order to reduce costs.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of these services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final message]&lt;/p&gt;
&lt;p&gt;The operation is now finished, no interruption of services.&lt;/p&gt;
&lt;p&gt;[Initial message]&lt;/p&gt;
&lt;p&gt;Thursday October 19 2023, starting at 12:00 UTC, we&amp;rsquo;ll proceed to the arm64 migration of the publick8s nginx ingress, hosting most of Jenkins Infrastructure public-facing services in order to reduce costs.&lt;/p&gt;
&lt;p&gt;There might be a brief interruption of these services.&lt;/p&gt;
&lt;p&gt;Related help desk issue: &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3619"&gt;https://github.com/jenkins-infra/helpdesk/issues/3619&lt;/a&gt;&lt;/p&gt;</content></item><item><title>[Resolved] mirrorbits migration</title><link>https://status.jenkins.io/issues/2023-06-12-mirrorbits-migration-to-publick8s/</link><pubDate>Mon, 12 Jun 2023 12:00:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2023-06-12-mirrorbits-migration-to-publick8s/</guid><category>2023-06-12T13:30:00-00:00</category><description>&lt;p&gt;[Final message]
Migration completed.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;mirrorbits&amp;rdquo; service from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Monday 12st of June 2023 at 12h00 UTC.
While there should not be any interruption, the corresponding service may be down for less than one hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586969797"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586969797&lt;/a&gt;.&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final message]
Migration completed.&lt;/p&gt;
&lt;p&gt;[Initial message]
A migration of the &amp;ldquo;mirrorbits&amp;rdquo; service from &lt;code&gt;prodpublick8s&lt;/code&gt; cluster to &lt;code&gt;publick8s&lt;/code&gt; cluster is planned today on Monday 12st of June 2023 at 12h00 UTC.
While there should not be any interruption, the corresponding service may be down for less than one hour.&lt;/p&gt;
&lt;p&gt;More details on &lt;a href="https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586969797"&gt;https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1586969797&lt;/a&gt;.&lt;/p&gt;</content></item><item><title>[Resolved] Maintenance on pkg.jenkins.io and mirrors.jenkins.io</title><link>https://status.jenkins.io/issues/2022-05-07-maintenance-pkg-mirror-jenkins-io/</link><pubDate>Sat, 07 May 2022 08:30:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-05-07-maintenance-pkg-mirror-jenkins-io/</guid><category>2022-05-07T09:13:00-00:00</category><description>&lt;p&gt;[Open Issue]
The VM hosting the services mirror.jenkins.io and pk.jenkins.io is slow to respond.
The person on-call received alerts last night and had to operate.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re going to increase the size of the VM and its disk as a short-term measure: both services will be down while the VM is restarted.&lt;/p&gt;</description><content type="html">&lt;p&gt;[Open Issue]
The VM hosting the services mirror.jenkins.io and pk.jenkins.io is slow to respond.
The person on-call received alerts last night and had to operate.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re going to increase the size of the VM and its disk as a short-term measure: both services will be down while the VM is restarted.&lt;/p&gt;</content></item><item><title>[Resolved] TLS error `SSL_ERROR_BAD_CERT_DOMAIN` on mirrors.jenkins.io and mirrors.jenkins-ci</title><link>https://status.jenkins.io/issues/2022-02-07-tls-mirrors/</link><pubDate>Mon, 07 Feb 2022 12:37:00 +0000</pubDate><guid>https://status.jenkins.io/issues/2022-02-07-tls-mirrors/</guid><category>2022-02-07T12:57:00-00:00</category><description>&lt;p&gt;[Final message]
The datadog alert on the https call &lt;a href="https://github.com/jenkins-infra/datadog/pull/56"&gt;has been removed&lt;/a&gt; as this service as never been served as https.&lt;/p&gt;
&lt;p&gt;[Initial message]
The services mirrors.jenkins-ci.org and mirrors.jenkins.io shows an error &lt;code&gt;SSL_ERROR_BAD_CERT_DOMAIN&lt;/code&gt; due to a certificate generated with the wrong name.
Only HTTPS (with TLS) access is impacted: plain HTTP is still working as expected.&lt;/p&gt;
&lt;p&gt;We are investigating the problem.&lt;/p&gt;</description><content type="html">&lt;p&gt;[Final message]
The datadog alert on the https call &lt;a href="https://github.com/jenkins-infra/datadog/pull/56"&gt;has been removed&lt;/a&gt; as this service as never been served as https.&lt;/p&gt;
&lt;p&gt;[Initial message]
The services mirrors.jenkins-ci.org and mirrors.jenkins.io shows an error &lt;code&gt;SSL_ERROR_BAD_CERT_DOMAIN&lt;/code&gt; due to a certificate generated with the wrong name.
Only HTTPS (with TLS) access is impacted: plain HTTP is still working as expected.&lt;/p&gt;
&lt;p&gt;We are investigating the problem.&lt;/p&gt;</content></item></channel></rss>