Starting January 1st 2022, Microsoft and Azul will no longer provide updates or support for the Zulu for Azure build of OpenJDK. While Java applications in production can continue to run without interruptions on these open source binaries – licensed under GPLv2 with Classpath Exception – quarterly bug fixes and security updates, and support will end on December 31, 2021. In addition, repositories, and the user download site for Zulu for Azure binaries may no longer be available after July 1st, 2022.
OpenJDK issues quarterly Patch Set Updates (PSU) on a community-aligned schedule: January, April, July, and October. This announcement provides more details on how Azure services will continue to provide secure and updated releases of Java, and how users can transition to other builds of OpenJDK.
For customers interested in continuing to use Azul’s OpenJDK-based distributions, Azul remains committed to publishing free updates of Azul Zulu builds of OpenJDK, with optional commercial support available through Azul.
Alternatively, customers can interchangeably use other OpenJDK distributions, such as Microsoft Build of OpenJDK, Eclipse Adoptium’s Temurin, or any other build of OpenJDK from different vendors.
Support for Azure Customers
Microsoft Azure customers will continue to receive support for Java applications without any extra cost. For more information, please visit Java Support on Azure.
For Azure services where Microsoft manages the Java runtime, services will gradually transition to OpenJDK distributions supported by Microsoft throughout the second half of 2021, following the release of July 2021 and October 2021 PSUs of OpenJDK for Java 8 and Java 11. These services will update the Java runtime according to their update plan or customer settings. Please consult the documentation of the service of your interest for more details and how this update may be reflected in your deployments.
Microsoft will use the following OpenJDK distributions for these services:
- Microsoft Build of OpenJDK for Java 11 and future versions.
- Eclipse Adoptium’s Temurin for Java 8.
For applications deployed to Azure services where Microsoft does not manage the Java runtime, customers may plan when and how to update Java and choose any JDK distribution.
Packages Availability Timeline
While we encourage customers to move to a different OpenJDK distribution as soon as practical, we understand this may take time. As such, Microsoft and Azul will continue to make all Zulu for Azure binaries available from the existing repositories managed by Azul until June 30th 2022 (i.e., 6 months beyond the end of updates and support). Customers with scripts (e.g., yum, apt-get, wget, curl, etc.) and CICD pipelines that directly download Zulu for Azure binaries from these repositories, will have additional time to plan their transition to a different OpenJDK distribution. After June 30th, 2022, Azul Zulu for Azure repositories may no longer host the Zulu for Azure binaries.
Container Images Availability Timeline
To ensure applications dependent on the Zulu for Azure images remain operational, images of Zulu for Azure will continue to be available until June 30th, 2022. We encourage customers to update their container builds to the latest versions of Zulu for Azure builds of OpenJDK for better security and performance enhancements and then start planning a transition to a new OpenJDK distribution.
Customers who want to continue to receive Java updates after December 31, 2021, must change their Dockerfiles. Customers can use equivalent Docker images from Azul, which are fully compatible and also built on OpenJDK, or a Docker image from different vendors. Please visit Microsoft’s Zulu for Azure repository and Azul’s Zulu builds of OpenJDK repository for a complete list of compatible Docker images.
Below we provide a list of interchangeable Docker images between Zulu for Azure and Azul Zulu builds of OpenJDK.
Zulu for Azure |
Azul Zulu builds of OpenJDK |
FROM mcr.microsoft.com/java/jdk:7-zulu-alpine |
FROM azul/zulu-openjdk-alpine:7 |
FROM mcr.microsoft.com/java/jdk:8-zulu-alpine |
FROM azul/zulu-openjdk-alpine:8 |
FROM mcr.microsoft.com/java/jdk:11-zulu-alpine |
FROM azul/zulu-openjdk-alpine:11 |
FROM mcr.microsoft.com/java/jdk:13-zulu-alpine |
FROM azul/zulu-openjdk-alpine:13 |
FROM mcr.microsoft.com/java/jdk:15-zulu-alpine |
FROM azul/zulu-openjdk-alpine:15 |
FROM mcr.microsoft.com/java/jdk:7-zulu-centos |
FROM azul/zulu-openjdk-centos:7 |
FROM mcr.microsoft.com/java/jdk:8-zulu-centos |
FROM azul/zulu-openjdk-centos:8 |
FROM mcr.microsoft.com/java/jdk:11-zulu-centos |
FROM azul/zulu-openjdk-centos:11 |
FROM mcr.microsoft.com/java/jdk:13-zulu-centos |
FROM azul/zulu-openjdk-centos:13 |
FROM mcr.microsoft.com/java/jdk:15-zulu-centos |
FROM azul/zulu-openjdk-centos:15 |
FROM mcr.microsoft.com/java/jdk:7-zulu-debian10 |
FROM azul/zulu-openjdk-debian:7 |
FROM mcr.microsoft.com/java/jdk:8-zulu-debian10 |
FROM azul/zulu-openjdk-debian:8 |
FROM mcr.microsoft.com/java/jdk:11-zulu-debian10 |
FROM azul/zulu-openjdk-debian:11 |
FROM mcr.microsoft.com/java/jdk:13-zulu-debian10 |
FROM azul/zulu-openjdk-debian:13 |
FROM mcr.microsoft.com/java/jdk:15-zulu-debian10 |
FROM azul/zulu-openjdk-debian:15 |
FROM mcr.microsoft.com/java/jdk:7-zulu-ubuntu |
FROM azul/zulu-openjdk:7 |
FROM mcr.microsoft.com/java/jdk:8-zulu-ubuntu |
FROM azul/zulu-openjdk:8 |
FROM mcr.microsoft.com/java/jdk:11-zulu-ubuntu |
FROM azul/zulu-openjdk:11 |
FROM mcr.microsoft.com/java/jdk:13-zulu-ubuntu |
FROM azul/zulu-openjdk:13 |
FROM mcr.microsoft.com/java/jdk:15-zulu-ubuntu |
FROM azul/zulu-openjdk:15 |
Important: Customers transitioning from Zulu for Azure Docker images based on unsupported or outdated Linux distributions (i.e., Debian 8, Debian 9, Ubuntu 18.04, and Ubuntu 19.10), should consider a change to a newer base OS.
Other Images and Packages
JRE
Developers can find Zulu for Azure JRE images under the “mcr.microsoft.com/java/jre:” prefix for the versions listed above. Azul’s Zulu builds of OpenJDK may contain JRE images that match the same version. To verify, append the suffix “-jre” to the image tag as listed in the table above, e.g., azul/zulu-openjdk:11-jre, and perform a ‘docker pull’ call to confirm availability.
JRE Headless
Developers can find Zulu for Azure JRE Headless images under the “mcr.microsoft.com/java/jre-headless:” prefix for the same versions listed above. Azul Zulu may contain JRE images that match the same version. To verify, append the suffix “-jre-headless” to the image tag as listed in the table above, e.g., azul/zulu-openjdk-alpine:13-jre-headless, and perform a ‘docker pull’ call to confirm availability.
Apache Maven
Developers can find Zulu for Azure with Apache Maven images under the “mcr.microsoft.com/java/maven” prefix, for Java 8 and Java 11, with Debian 9 and Debian 10 as base OS. Developers may move to the official Apache Maven images available on Docker Hub. Azul Zulu may also contain images with Maven; check the Azul Zulu repository for availability.
Apache Tomcat
Developers can find Zulu for Azure with Apache Tomcat images under the “mcr.microsoft.com/java/tomcat” prefix for Java 8 and Java 11 with Debian 10, Ubuntu 20.04, Alpine 3.12, and CentOS 8 as base OS. Developers may move to the official Apache Tomcat images available on Docker Hub. Azul Zulu may also contain images with Tomcat; check the Azul Zulu repository for availability.
Windows Images
Developers can find Zulu for Azure images for Windows Server Core. Customers who want to continue to receive updates of OpenJDK with these images will have to write and build their images and use a different OpenJDK distribution than Zulu for Azure. Developers can find the source code originally used to create these images on GitHub.
Important Dates
- July 20th, 2021: Q3 Java PSU releases.
- October 19th, 2021: Q4 Java PSU releases (last Zulu for Azure update).
- January 1st, 2022: End of updates and support for Zulu for Azure binaries.
- July 1st, 2022: Zulu for Azure binaries may no longer be available from Azul Zulu for Azure repositories. Docker images may no longer be available on Docker Hub or in the Microsoft Container Registry.
If you have further questions, please contact openjdk-support@microsoft.com.
0 comments