Update azure clusters publick8s Kubernetes version to 1.27

accounts.jenkins.io admin.accounts.jenkins.io cert.ci.jenkins.io ci.jenkins.io get.jenkins.io incrementals.jenkins.io infra.ci.jenkins.io issues.jenkins.io javadoc.jenkins.io jenkins-wiki-exporter.jenkins.io jenkins.io ldap.jenkins.io mirrors.jenkins-ci.org mirrors.jenkins.io plugin-health.jenkins.io plugin-site-issues.jenkins.io plugins.jenkins.io plugins.origin.jenkins.io release.ci.jenkins.io repo.azure.jenkins.io reports.jenkins.io stories.jenkins.io trusted.ci.jenkins.io uplink.jenkins.io wiki.jenkins.io www.jenkins.io

[Final Message] The operation finished successfully at 9:35am UTC.

More details on https://github.com/jenkins-infra/helpdesk/issues/3948#issuecomment-1991181964.

[Initial message] We’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).

The expected impacts are:

Restart of the following service, with an outage (between 2 to 15 min: depends on Azure Storage systems):

• ldap.jenkins.io
• weekly.ci.jenkins.io
• incrementals.jenkins.io

Temporary disruptions (no Log-In/log-out possible during the LDAP restart) on:

• accounts.jenkins.io
• ci.jenkins.io, trusted.ci.jenkins.io, infra.ci.jenkins.io, weekly.ci.jenkins.io, release.ci.jenkins.io, cert.ci.jenkins.io
• issues.jenkins.io (JIRA)

Temporary disruptions (slow requests or outage of a few minutes) due to public IP metadata changes and falco + Nginx upgrades:

• get.jenkins.io (mirror redirector)
• javadoc.jenkins.io
• jenkins-wiki-exporter.jenkins.io
• plugins.jenkins.io
• repo.azure.jenkins.io
• reports.jenkins.io
• stories.jenkins.io
• uplink.jenkins.io
• www.jenkins.io