Portainer Business Updates & Release Notes

September 17, 2026

Known Issues <a href="#known-issues" id="known-issues"></a>

• On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot
• kubectl port-forward fails with Portainer kubeconfig in some configurations

Known issues with Podman

• Support for only CentOS 9, Podman 5 rootful
• Auto onboarding a Podman environment defaults to “Standard” and not “Podman”
• It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)

Known issues with Talos clusters managed by Omni (BE only)

• Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster

New in this release <a href="#new-in-this-release" id="new-in-this-release"></a>

• Hardened outbound requests against SSRF. Helm chart resolution and Git HTTP/HTTPS operations now go through the SSRF-aware transport, and the static rules that enforce this now match by type rather than by import alias, so an aliased import can no longer slip past them
• Certificate-based authentication for Azure Blob backups is now disabled in FIPS mode
• Added build-time static analysis that catches FIPS violations before they ship …

August 27, 2026

Known Issues <a href="#known-issues" id="known-issues"></a>

• On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot
• kubectl port-forward fails with Portainer kubeconfig in some configurations

Known issues with Podman

• Support for only CentOS 9, Podman 5 rootful
• Auto onboarding a Podman environment defaults to “Standard” and not “Podman”
• It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)

Known issues with Talos clusters managed by Omni (BE only)

• Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster

New in this release <a href="#new-in-this-release" id="new-in-this-release"></a>

New and improved features

• Added advanced Kubernetes node drain options with agent failover
• Added native Portainer APIs for writing Kubernetes secrets, configmaps, deployments and persistent volume claims, replacing direct kube-apiserver proxy calls
• Added a generic Kubernetes manifest dry-run API
• Edge Compute settings can now be configured during initial setup and via cli flags …

August 13, 2026

Known Issues <a href="#known-issues" id="known-issues"></a>

• On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot
• kubectl port-forward fails with Portainer kubeconfig in some configurations

Known issues with Podman

• Support for only CentOS 9, Podman 5 rootful
• Auto onboarding a Podman environment defaults to “Standard” and not “Podman”
• It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)

Known issues with Talos clusters managed by Omni (BE only)

• Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster

New in this release <a href="#new-in-this-release" id="new-in-this-release"></a>

Bug Fixes

• Fixed a user's direct environment access being incorrectly removed when a team they belonged to was deleted
• Fixed multiple "Cannot read properties of undefined (reading 'message')" error toasts appearing on Kubernetes application pages when an API call failed without a response (e.g. while pods are restarting after a redeploy)
• Fixed an "Invalid Swarm ID" / 503 error when creating a stack from a Swarm worker node …

July 30, 2026

Known issues <a href="#known-issues" id="known-issues"></a>

• On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot.
• In some Portainer Server Kubernetes installs, removing the local Kubernetes environment can prevent add-ons from being detected or managed correctly. For more information and a workaround, see this FAQ.
• When creating a GitOps workflow, Compose files not named docker-compose.yml or compose.yml are detected as Kubernetes manifests, so Docker edge groups aren't offered as deployment targets.

Known issues with Podman support

• Support for only CentOS 9, Podman 5 rootful.

Known issues with Talos clusters managed by Omni (BE only)

• Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster.

New in this release <a href="#new-in-this-release" id="new-in-this-release"></a>

New and improved features

• Added a basic workflow details screen
• Added GPU visibility in the Environment Details view
• Made the Portainer setup token easier to spot in the installation logs …

July 14, 2026

Known Issues

• On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot
• kubectl port-forward fails with Portainer kubeconfig in some configurations

Known issues with Podman

• Support for only CentOS 9, Podman 5 rootful
• Auto onboarding a Podman environment defaults to “Standard” and not “Podman”
• It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)

Known issues with Talos clusters managed by Omni (BE only)

• Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster

New in this Release

• Fixed a 2.39.4 regression where a relative env_file: in a Git stack whose compose file lives in a repository sub-directory was resolved against the project root instead of the compose file's own directory, deploying stacks with an empty environment or failing outright
• Improved Edge tunnel reliability over high-latency links (satellite/VSAT): the server no longer tears down a half-established tunnel on timeout, keep-alive and unlimited background retries were added on the agent, and the ping timeout was raised from 3s to 8s …