Jenkins Phasing Out Windows Server 2019 Agent Containers, Urging Migration

The Jenkins project has announced the end-of-life (EOL) for official support and delivery of Windows Server 2019 container images for its inbound and SSH agents, effective August 21, 2026. This decision follows Jenkins core stopping support for these images in versions 2.569 and 2.568.1. The primary driver for this change is the retirement of Windows Server 2019 from Azure Kubernetes Service (AKS) on March 1, 2026, which means AKS no longer provides new node images or security patches for this version, rendering existing node pools unsupported. This development carries significant implications for DevOps teams and practitioners leveraging Jenkins, particularly those operating on Windows-based build agents or within cloud environments like Azure Kubernetes Service. The immediate impact is the cessation of official Jenkins-provided Windows Server 2019 agent container images. This means that any CI/CD pipelines configured to use these images will either need to be updated to newer Windows Server versions (2022 or 2025) or teams will have to assume the burden of building and maintaining their own custom Windows Server 2019 agent images. The risk extends beyond mere inconvenience; continuing to use unsupported images exposes build environments to potential security vulnerabilities, as they will no longer receive critical security patches. This could compromise the integrity of the entire software supply chain. This move aligns with a broader industry trend towards modernizing infrastructure and maintaining up-to-date operating environments. Cloud providers are continually evolving their supported offerings, and older versions of operating systems eventually reach their end-of-life, leading to a ripple effect across the ecosystem of tools built upon them. We've seen similar deprecations and EOL announcements for various components in the cloud-native landscape, pushing organizations to regularly review and update their foundational infrastructure. The emphasis on containerization and immutable infrastructure further highlights the need for standardized, secure, and actively maintained base images. In practice, organizations should immediately audit their Jenkins environments to identify any reliance on Windows Server 2019 agent containers. The recommended course of action is to plan and execute a migration to Windows Server 2022 or 2025. This migration should involve thorough testing of existing pipelines to ensure compatibility and stability with the newer operating system versions. For teams that cannot immediately migrate, building and maintaining custom Windows Server 2019 images is a temporary workaround, but this introduces additional operational overhead and responsibility for security patching. This event serves as a crucial reminder for continuous vigilance in managing CI/CD infrastructure dependencies, emphasizing the importance of staying current with underlying platform and operating system versions to maintain security, performance, and supportability.