Batch Support for CentOS 7 Ending
Summary
Azure Batch will retire support for CentOS 7 aligned operating systems to follow the publisher ending standard support on June 30, 2024. If your workload utilizes Batch pools based on this OS, either via Marketplace images (directly from OpenLogic/RogueWave/Perforce/microsoft-azure-batch or derived from by other publishers) or your own custom images including compute image gallery, then you will need to take action. Please migrate your workload to a publisher supported version of an Enterprise Linux or derivative VM image such as Red Hat Enterprise Linux (RHEL), or AlmaLinux. On 2024-07-01, Azure Batch will remove support for the batch.node.centos 7 compute node agent. Afterwards, create pool and resize up operations for associated pools may fail. Existing pools may be subject to forced scale in to zero nodes at any point after this date. Customers who continue to use these pools past the indicated Batch support End of Life will be subject to potential security risks.
Migration possibilities
Please note that any Batch pool specifying the batch.node.centos 7 node agent is subject to end of life.
| Current OS | Migration Target Publisher:Offer:Sku | Node Agent | Restrictions | Additional Information | Notes |
|---|---|---|---|---|---|
| CentOS 7.x | almalinux:almalinux:9-gen1 |
batch.node.el 9 | None | Link | Gen1 image |
almalinux:almalinux:9-gen2 |
batch.node.el 9 | None | Link | Gen2 image | |
redhat:rhel:9_1 |
batch.node.el 9 | User subscription accounts | Link | Gen1 image | |
redhat:rhel:91-gen2 |
batch.node.el 9 | User subscription accounts | Link | Gen2 image | |
| CentOS-HPC 7.x | almalinux:almalinux-hpc:8-hpc-gen1 |
batch.node.el 8 | None | Link | Gen1 image, IB/IB+GPU VM Sizes, container workloads |
almalinux:almalinux-hpc:8-hpc-gen2 |
batch.node.el 8 | None | Link | Gen2 image, IB/IB+GPU VM Sizes, container workloads |
Please consult the List Supported Images API for the latest versions available.
More information
Azure Batch VM Size and Image Guide Azure Batch Best Practices