Skip to content

Releases: portainer/portainer

Release 2.20.2

30 Apr 21:47
eb5b9ef
Compare
Choose a tag to compare
Release 2.20.2 Pre-release
Pre-release

2.20.2

See Upgrading Portainer instructions.

Overview of Changes

Introducing the new Portainer CE 2.20.2 release. This is an STS (Short-Term Support) release.

As you gear up for the transition to Portainer CE 2.20.2, our latest STS (Short-Term Support) installment, ensuring a smooth upgrade is key. We urge you to back up your configurations via the Portainer UI beforehand. This backup acts as your safety net, ensuring you can gracefully revert to the prior version or state if the new frontier proves too wild. Additionally, pore over the release notes for catching any compatibility issues, understanding deprecated functionalities, and identifying essential tweaks to your current setup. Your diligence will pave the way for a seamless update.

A Short-Term Support release can be considered as "bleeding-edge" as it will contain the latest features and functionality we've developed. The STS releases (including this one) will go through a significant amount of pre-release testing, but there may be changes that could cause regressions and features that might see further iterations. As such, if stability is a crucial concern for your setup we wouldn't recommend deploying STS releases on production environments.

Read more in our "Portainer 2.20 STS" blog

Resolved CVEs

Edge

  • Resolved an issue with the edge post initiation migration runner to ensure it runs migrations at the appropriate time, when connection between an edge environment and Portainer server has been established. portainer/portainer#11733

Docker

  • Resolved an issue that caused errors when users attempted to connect to their Docker environment via API using HTTPS portainer/portainer#11721
  • Provided info text in the UI to clearly explain environment variables stack.env file usage when deploying Docker stacks via Git vs. other methods. portainer/portainer#11732

Kubernetes

  • Ensured confirmed support of vanilla Kubernetes 1.30 clusters. portainer/portainer#11730
  • Resolved an issue with Kubernetes environments that have a significant number of services where the Dashboard services panel never completed loading and the loading spinner was indefinitely displayed. portainer/portainer#11734

Portainer

  • Fixed an issue introduced in 2.20.0 where a user logged in using external SSO could no longer create a Portainer API access token. portainer/portainer#11731
  • Fixed an issue where redeploying a git-based deployment failed due to the target path already existing portainer/portainer#11722
  • Resolved an issue where pending actions to be run on environments would still be considered for deleted environments (although not actually run). portainer/portainer#11735
  • Resolved issue where containers that exited with code 0 were incorrectly marked as failed deployments portainer/portainer#11724
  • Introduced an additional option to automatically detect the authentication style for OAuth portainer/portainer#11725

API Changes

Modified endpoints

  • PUT /settings Update Portainer settings

    Parameters

      Added: body.OAuthSettings.AuthStyle
    
    

    Return Type

      Added: OAuthSettings.AuthStyle
    
    
  • GET /settings Retrieve Portainer settings

    Return Type

      Added: OAuthSettings.AuthStyle
    
    
  • PUT /settings/default_registry Update Portainer default registry settings

    Return Type

      Added: OAuthSettings.AuthStyle
    
    
  • POST /users/{id}/tokens Generate an API key for a user

    Return Type

      Added: apiKey
      Added: rawAPIKey
    
    

Release 2.19.5

21 Apr 21:10
9191d31
Compare
Choose a tag to compare

2.19.5

See Upgrading Portainer instructions.

Overview of changes

New Portainer CE 2.19.5 release

Portainer

  • Resolved CVE-2024-29296 by creating uniform response time for login attempts

Release 2.20.1

04 Apr 23:16
b284d70
Compare
Choose a tag to compare

2.20.1

See Upgrading Portainer instructions.

Overview of changes

Introducing the new Portainer CE 2.20.1 release. This is an STS (Short-Term Support) release.

As you gear up for the transition to Portainer CE 2.20.1, our latest STS (Short-Term Support) installment, ensuring a smooth upgrade is key. We urge you to back up your configurations via the Portainer UI beforehand. This backup acts as your safety net, ensuring you can gracefully revert to the prior version or state if the new frontier proves too wild. Additionally, pore over the release notes for catching any compatibility issues, understanding deprecated functionalities, and identifying essential tweaks to your current setup. Your diligence will pave the way for a seamless update.

A Short-Term Support release can be considered as "bleeding-edge" as it will contain the latest features and functionality we've developed. The STS releases (including this one) will go through a significant amount of pre-release testing, but there may be changes that could cause regressions and features that might see further iterations. As such, if stability is a crucial concern for your setup we wouldn't recommend deploying STS releases on production environments.

Read more in our "Portainer 2.20 STS" blog

Important Note Regarding Docker 26 Support

Please be aware that support for Docker 26 is provided on an "as-is" basis and is primarily driven by best-effort principles. Minimal regression testing has been conducted to ensure basic functionality. Users should proceed with caution and report any issues they encounter.

Docker

  • Resolved an issue where Docker 25/26 API changes affected container-related pages and image size display portainer/portainer#11504

Kubernetes

  • Resolved an issue where deploying GitOps edge stacks on a Kubernetes edge device resulted in error portainer/portainer#11503
  • Resolved an issue where the secret owner migration process could lead to a deadlock, preventing the HTTP(S) server from starting. portainer/portainer#11501

Portainer

  • Fixed an issue where local stacks were being overwritten by orphaned stacks with the same name in the regular stack listing page portainer/portainer#11502

Release 2.20.0

19 Mar 01:12
6a3eda4
Compare
Choose a tag to compare

2.20.0

See Upgrading Portainer instructions.

Overview of changes

Introducing the new Portainer CE 2.20.0 release. This is an STS (Short-Term Support) release.

As you gear up for the transition to Portainer CE 2.20.0, our latest STS (Short-Term Support) installment, ensuring a smooth upgrade is key. We urge you to back up your configurations via the Portainer UI beforehand. This backup acts as your safety net, ensuring you can gracefully revert to the prior version or state if the new frontier proves too wild. Additionally, pore over the release notes for catching any compatibility issues, understanding deprecated functionalities, and identifying essential tweaks to your current setup. Your diligence will pave the way for a seamless update.

A Short-Term Support release can be considered as "bleeding-edge" as it will contain the latest features and functionality we've developed. The STS releases (including this one) will go through a significant amount of pre-release testing, but there may be changes that could cause regressions and features that might see further iterations. As such, if stability is a crucial concern for your setup we wouldn't recommend deploying STS releases on production environments.

Read more in our "Portainer 2.20 STS" blog

Breaking Changes

  • Introduced a requirement to specify the current user's password when adding an API token via the UI or the POST /users/{id}/tokens API endpoint.
  • Fixed issue when deploying Docker stacks from Git-based custom templates where a user could edit the content via the web editor, when they should only have been able to deploy the content from Git.

Deprecation Notice

  • DEPRECATED API endpoint GET /kubernetes/{id}/namespaces/{namespace}/configuration. Following Portainer 2.19 split of K8s ConfigMaps and Secrets to two UI tabs and K8s API proxy use, the original endpoint combining both resource types is marked deprecated.
  • DEPRECATED API endpoint GET+POST /endpoints/{id}/kubernetes/helm/repositories, MOVED Helm UI option to Advanced Deployment/Create from Manifest screen + now allow users to delete their Helm repos. New endpoint GET+POST /users/{id}/helm/repositories added.

Resolved CVEs

  • Updated various packages to resolve CVEs. portainer/portainer#9224
  • Resolved CVEs for Portainer agent
  • Resolved CVEs for Portainer CE and BE

Edge

  • Fixed issue where admin users were unable to update a Git-based edge stack created by another user.
  • Fixed issue where the "Retry deployment" toggle did not persist when editing an edge stack.
  • Fixed issue clearing logs for edge jobs, addressing an error related to the absence of the specified directory
  • Resolved an issue by implementing timeouts for the agent during snapshot building, preventing it from getting stuck indefinitely or taking excessive time in unresponsive Docker daemon scenarios
  • Fixed an issue where the Edge Agent was resetting EndpointId to 0 and polling global-key incorrectly when disconnected from Portainer server, even with disabled edge compute features
  • Fixed an issue where a dynamic edge group would erroneously create a stack even if no environment was present

Swarm

  • Updated the documentation link for Swarm agent setup in the UI to ensure it directs users to the correct documentation.
  • Updated the Quick Setup wizard to provide a more accurate message, eliminating misleading connection failure notifications when adding the local environment via Agent deployment.

Docker

  • Fixed issue where Docker Images List breaks when an image has no tags.

Kubernetes

  • Updated the version of the kubectl client in the kubectl shell console. portainer/portainer#11303
  • Fixed the stripping of labels from certain Kubernetes resources - Ingress, ConfigMap or Secret - when form-editing them. portainer/portainer#11147
  • Resolved an issue where, on adding a Helm repo, a timeout could sometimes occur. portainer/portainer#11137
  • Resolved an issue where the upgrade to BE from CE within Portainer on MicroK8s was failing because the wait time was too short.
  • Fixed an issue where namespaces 'set to system' from within Portainer weren't being detected as system. portainer/portainer#11146
  • Fixed 'Unable to determine which association to use to convert form' error when adding a service to a Kubernetes pod that had been deployed external to Portainer. portainer/portainer#11136
  • Corrected a minor UI issue introduced in 2.19.0, where, on create of Kubernetes application, if the user scrolled down and clicked 'Add persisted folder' without populating name and image fields, the focus would jump up to the first empty required field. portainer/portainer#11155
  • Fixed an issue introduced in 2.19 in the ConfigMaps and Secrets lists where a check was no longer made against them for deployments of type Pod and hence an 'Unused' badge in those instances was then not shown. portainer/portainer#11145
  • Fixed a 'this.formValues.Services is undefined' error that was shown when editing a pod created via manifest. portainer/portainer#11152
  • Resolved an issue where ConfigMaps and Secrets created via manifest were incorrectly shown with the 'External' badge. portainer/portainer#11169
  • Corrected showing of a blank screen when editing a Kubernetes application that had been deployed external to Portainer, so that the Edit application screen is now shown. portainer/portainer#11161
  • Introduced a per-user option to enable five-minute data caching for non-edge Kubernetes environments - to improve performance. portainer/portainer#11118
  • Fixed the Kubernetes Application details screen not showing referenced resources for an app that had used 'envFrom:' in its manifest to load an entire ConfigMap or Secret as environment variables instead of referencing individual values via 'valueFrom:'. portainer/portainer#11144
  • Introduced a setting to turn off the Stacks functionality within the Kubernetes side of Portainer. portainer/portainer#11119
  • Renamed the Kubernetes Advanced Deployment screen to be 'Create from Manifest'. portainer/portainer#11128
  • Corrected display of a very high 'CPU used' value in the Kubernetes Cluster details screen when micro-CPU units were being used. portainer/portainer#11154
  • DEPRECATED API endpoint GET+POST /endpoints/{id}/kubernetes/helm/repositories, MOVED Helm UI option to Advanced Deployment/Create from Manifest screen + now allow users to delete their Helm repos. New endpoint GET+POST /users/{id}/helm/repositories added. portainer/portainer#11127
  • Resolved issues that occurred around editing a Kubernetes application when a namespace had resource quotas set, where the application's (pre-edit) existing resource usage was not being taken into account. portainer/portainer#11143
  • Introduced a change so that, on deletion of an ECR or other registry, any related Kubernetes registry secret will now be removed. Note that this type of secret is auto created when assigning a registry to a namespace in a Kubernetes environment. portainer/portainer#11158
  • Migrated the Kubernetes Application Details screen's YAML, Events and Containers sections plus any of the screen's remaining code from Angular to React. portainer/portainer#11121
  • Fixed an issue around the display of incorrect search results for Kubernetes applications that are exposed via an ingress. portainer/portainer#11160
  • Corrected the Kubernetes Volume Details screen to show the Shared Access Policy of the Volume rather than (erroneously) of the StorageClass. portainer/portainer#11163
  • Corrected the deploying of a Kubernetes Daemonset with shared storage so that RWX access is granted to the Persistent Volume Claim, as relevant. portainer/portainer#11168
  • Migrated the Kubernetes Cluster Setup screen from Angular to React and improved loading of its elements. portainer/portainer#11122
  • Introduced a change so that, on assigning a user access to a Kubernetes environment that is down, the access is enabled when the environment next connects. portainer/portainer#11157
  • Corrected the display of the 'Allow resource over-commit' setting in Portainer CE, which was showing as off even though the functionality has always operated as though it is on. Note that no actual changes to functionality have been made. portainer/portainer#11142
  • Fixed a console error that could arise in the Kubernetes Add/Edit Application screen when updating resource sliders. [#11159](https://github.com/portainer/portainer/i...
Read more

Release 2.19.4

07 Dec 08:37
90a160e
Compare
Choose a tag to compare

2.19.4

See Upgrading Portainer instructions.

Overview of changes

New Portainer CE 2.19.4 release

Swarm

  • Resolved the inability to change the replica set for a swarm service, addressing errors related to invalid CredentialSpec (A refresh of your browser cache may be required)
    #10702

Release 2.19.3

21 Nov 23:03
cd9ad97
Compare
Choose a tag to compare

2.19.3

See Upgrading Portainer instructions.

Overview of changes

New Portainer CE 2.19.3 release

Portainer

  • Resolved an issue where polling and webhook methods failed to update the Stack #10673

Release 2.19.2

13 Nov 01:22
280a2fe
Compare
Choose a tag to compare

2.19.2

See Upgrading Portainer instructions.

Overview of changes

New Portainer CE 2.19.2 release

Swarm

  • Resolved an issue where the Docker service page could not load correctly when the deployment was created using the GMSA credential spec parameter. #10571

Kubernetes

  • Introduced the ability for Helm chart repository searching and registry browsing to operate behind a forward proxy. #10432

Portainer

  • Introduced a calmer and more reserved look for the business feature highlights shown in the community edition, as we want to indicate what's possible without imposing too much on the user. #10435
  • Improved security around non-admin user environment information access. #10434
  • Resolved an issue where stacks that were initially deployed from a template could not be modified. #10563
  • Resolved an issue where users couldn't define a proxy for the agent and edge agent when their network relied on a proxy for internet access. #10564
  • Resolved an issue where pulling and redeploying Git stacks took longer than expected. #10565
  • Resolved an issue where stacks triggered from webhooks were marked as inactive status, even though they were running as expected #10567
  • Resolved an issue where users could interact with a console even after logging out from another tab in the browser #10568
  • Resolved an issue where there was no warning for version mismatch between the server and edge agent, now UI clearly indicates matching server and edge agent versions are required for feature availability. #10569

Rest API Changes

  • Improved security around non-admin users and their permissions. #10434

Modified Endpoints: 1

POST /auth/logout

  • Description changed from 'Access policy: authenticated' to 'Access policy: public'

Release 2.19.1

20 Sep 10:17
8f42ba0
Compare
Choose a tag to compare

See Upgrading Portainer instructions.

Overview of changes

New Portainer CE 2.19.1 release

Breaking Changes

  • Changes to API format and checking of some requests - See rest API changes below for more details.

Portainer

  • Fixed an issue where backup files were missing the Chisel private key. This could have disrupted communication between the Portainer server and agent after a restoration from backup. #10335
  • Improved the upgrade process for the Portainer server, upgrade process now halts on database migration errors, preventing database version mismatches for a more stable environment. #10336
  • Fixed an issue where toggles could be activated outside of their intended component area, potentially leading to inadvertent toggling. #10324

Rest API Changes

  • Fixed an issue introduced in 2.19.0 when Kubernetes environment metrics API features were enabled, where these features would return an β€˜Unable to reach metrics API’ error.
  • Introduced new format around the change of a user’s password via API. #10326
  • Updated the checking around change of a user via API. #10326
  • Fixed API endpoints that were broken in the 2.19.0 release, ensuring that they retain their previous functionality. #10337

Release 2.19.0

04 Sep 03:49
7abed62
Compare
Choose a tag to compare

2.19.0

See Upgrading Portainer instructions.

Overview of changes

New Portainer CE 2.19.0 release

Breaking Changes

  • A number of components/views have been migrated from Angular to React.
  • Internal versioning on stacks feature has introduced file structure changes in 2.19.
  • We have addressed an API issue in which an incorrect parameter was being used for API endpoint /edge_groups. Users relying on the HasEdgeGroup parameter should now use HasEdgeJob to achieve the intended functionality.
  • Four API endpoints are broken and will be restored in the next release POST /custom_templates, POST /edge_jobs, POST /edge_stacks, POST /stacks

Resolved CVE's

Edge

  • Fixed an issue where deploying a large volume edge stack triggered a 'URI too large' error. portainer/portainer#10128
  • Fixed an API issue where the incorrect parameter HasEdgeGroup was being used instead of HasEdgeJob for endpoint /edge_groups. Users relying on the HasEdgeGroup parameter should now use HasEdgeJob to achieve the intended functionality. portainer/portainer#10133
  • Improved logging for edge agent when polling fails. This enhancement provides more informative and detailed logs when polling encounters failures, aiding in quicker identification and resolution of issues. portainer/portainer#10143
  • Resolved an issue where users were able to create schedulers with an empty edge group, which is no longer allowed to ensure proper functionality and avoid potential errors portainer/portainer#10149
  • Resolved an issue where the edge agent default poll frequency selector was not lining up correctly portainer/portainer#10150
  • Resolved an issue where users were unable to create an edge group when there were no members present in that group. Edge groups can now be created without requiring initial members, offering greater flexibility in edge device and configuration management. portainer/portainer#10153
  • Introduce an enhancement to our snapshot creation process for edge devices which streamlines the snapshot creation experience, providing users with a more efficient and user-friendly way to capture snapshots on edge devices. portainer/portainer#10154
  • Fixed an issue where environment files were not functioning properly in Git deployments for edge stacks. portainer/portainer#10171
  • Introduced webhooks for edge stack, you can now set up webhooks for your edge stacks, enabling automated polling for GitOps updates. portainer/portainer#10178
  • Fixed an issue where the agent was unintentionally flushing edge job entries when collecting logs. portainer/portainer#10172

Docker

  • Addressed an issue where the Docker client was not utilising version negotiation. portainer/portainer#10125
  • Resolved an issue where the image name was displayed incorrectly when a user tried to duplicate or edit a container portainer/portainer#10126
  • Fixed an issue in the API where sending files to a Docker endpoint resulted in a panic. portainer/portainer#10129
  • Resolved an issue with Docker Proxy's performance, resulting in improved overall performance and responsiveness when using the Docker Proxy feature. portainer/portainer#10131
  • Resolved an issue in the Docker Container List where searching by published ports was no longer working. portainer/portainer#6656
  • Resolved an issue where '.' was not allowed in the image name (but should be) when building a Docker image via the UI. portainer/portainer#8047
  • Resolved some minor UI issues in Docker Services-related screens. portainer/portainer#10117

Swarm

  • Fixed an issue in Docker Swarm version 24.0.0 where image tags were not being displayed. portainer/portainer#10134
  • Resolved an issue where clicking into the details page of a Swarm stack would redirect users to the service section instead of the top of the page portainer/portainer#10151

Kubernetes

  • Adjusted Kubernetes Cluster setup screen's ingress settings to be clearer and to give info on ingress defaults. portainer/portainer#10101
  • Resolved an issue with Kubernetes ECR image pull where the secret token was not updating on manifest deployment. portainer/portainer#10119
  • Migrated the Kubernetes Add/Edit Application screen's Services section from Angular to React. portainer/portainer#9235
  • Reintroduced the ability to specify and use (via Add/Edit Application) ingress defaults (hostname and annotations). portainer/portainer#10030
  • Reintroduced the ability to publish via ingress from the Add/Edit Application screen. portainer/portainer#10103
  • Introduced correct redirecting of the user, following deployment of a Kubernetes manifest. Previously the user was always returned to the Applications List but will now arrive back at the screen from which they accessed the Advanced Deployment function. portainer/portainer#10115
  • Migrated the Kubernetes Application Details screen's Summary and Details sections from Angular to React. portainer/portainer#10102
  • Introduced a loading spinner to the Add/Edit ingress screen's ingress class dropdown, to indicate that available options are still being retrieved. portainer/portainer#10000
  • Resolved an issue that was occurring on the exposing of Portainer over a subpath, where Kubernetes Cluster Setup and other screens failed to load and reported an error. portainer/portainer#10112
  • Resolved a Node details issue where nodes showed incorrect role of 'Worker' due to deprecated 'node-role.kubernetes.io/master' K8s label (now 'control-plane'). Also where MicroK8s cluster nodes were incorrectly identified (though not due to labels). portainer/portainer#10104
  • Split the Kubernetes ConfigMaps & Secrets functionality in order to provide better performance and a clearer user experience. We now have separate tabs in the list screen and separate add/edit functions. portainer/portainer#9222
  • Resolved an issue with Kubernetes pages where a warning showed in the browser console ('findDOMNode is deprecated in StrictMode') when resource assignment was first toggled on for the namespace. portainer/portainer#10111
  • Updated Kubernetes ConfigMaps & Secrets terminology that was previously shown as Configurations, so as to align more clearly with Kubernetes. portainer/portainer#10025
  • In the Dashboard screen of Kubernetes environments, Ingresses and Services panels have now been introduced, providing a count of these resources and an easy means to click through and access their list screens. portainer/portainer#9223
  • Migrated Kubernetes Application console page from Angular to React. portainer/portainer#9177
  • Introduced a feature that lets you upgrade your Portainer Community Edition to the Business Edition right within Portainer on Kubernetes platform. portainer/portainer#10177
  • Resolved an issue where the Helm repository URL in (Kubernetes) Settings could not be updated.

Portainer

  • Fixed an issue where a bad gateway response occurred when updating an environment with an empty URL. portainer/portainer#10123
  • Resolved an issue where users were unable to deploy a stack when utilising an image from a private GitLab r...
Read more

Release 2.18.4

06 Jul 23:36
a5bb862
Compare
Choose a tag to compare

2.18.4

See Upgrading Portainer instructions.

Overview of changes

New Portainer CE 2.18.4 release

Resolved CVEs

Docker

  • Upgraded Docker Compose version to v2.17.2 for Portainer Agent #9095
  • Resolve a problem building Portainer due to an issue with v1.53.0 of golangci-lint. #9057

Swarm

  • Resolved an issue where users were unable to migrate or duplicate their swarm stack #9097

Portainer

  • Resolved an issue where the static IP addresses in a macvlan were unexpectedly changed #9101
  • Enhanced the user experience of the 'Skip TLS Verification' feature by adding a confirmation modal #9098
  • Resolved an issue where recreate containers fail when it has a shared and external volumes #9102

REST API Changes

  • Resolved an issue where the response from the API was inconsistent when querying all endpoints and a specific endpoint #9096