Portainer 2.39 LTS brings Fleet Governance Policies, alerting, and shared Git credentials

Portainer 2.39 LTS introduces several updates aimed at making container management more scalable and user-friendly. This release features Fleet Governance Policies, which provide administrators with new ways to govern container infrastructure on a large scale. Alerting moves out of experimental status and is now generally available, allowing administrators to set up notifications for situations such as offline environments, failed backups, or high resource usage.

Following these core platform changes, Docker stack workflows gain the ability to rename stacks during duplication or migration, increasing flexibility for migration scenarios. Admins can now centrally manage shared Git credentials from the Shared Credentials view, enabling secure reuse across deployments and templates without exposing underlying secrets.

With the ongoing refactor to React, the registry repository management view has been redesigned, resulting in simpler tag management. For Kubernetes workflows, Portainer now lets administrators inspect Custom Resource Definitions and associated custom resources directly in the interface. In addition, users have gained the ability to view node YAML details, aiding troubleshooting and auditing.

Additionally, Helm chart deployments can now be managed straight from Git repositories, with a Manifest preview shown alongside values YAML at creation or upgrade. Edge stack users working with relative path volumes will find a new “Always clone” option for improved handling.