Portainer fans will be very excited because a new version came out recently. We are going to see the changes that came in this release and also going to explore the features. We will also see the issues and bugs that got fixed to maintain stability and improve user experience.
In this release, we can see the introduction of the ability to deploy a manifest from a git repository when using advanced deployment. For more information, click here.
Again, we can see the renaming of resource pools to namespaces in the user interface.
Now, standard users can also use advanced deployment features.
While deploying a Kubernetes resource, users can get a summary of Kubernetes actions.
Another new functionality allows multiple ingress networks per Kubernetes namespace, with a differing config per ingress.
Now users can see real-time container metrics in Kubernetes.
The new release also comes with the ability to display real-time node metrics in Kubernetes.
Now application image names will come with improved visualization.
The new release shows the improved UI for placement policies while creating an application.
We can see fixing an issue from the previous release where the advanced deployment does not work when using an agent.
The new release fixed another issue where environment variable validation when creating an application was too restrictive.
Also, this version fixed the issue where adding an application does not allow the setting of Global.
Again, we can see fixing the issue where the endpoint URL is not updated when updating a Kubernetes local endpoint.
The release also fixed another issue which showed whenever a docker endpoint is selected, configuring a newly added k8s agent fails.
With the new release, cleaning of namespace access will happen while removing users from the endpoint.
The new update added the ability to update and redeploy a stack created from a git repository.
We can now see enhanced environment variables UI/UX for Docker.
Container statistics will now show I/O usage in the new release.
There will be no issue regarding stacks with a status of zero getting hidden in the UI.
Now, deploying the stack from Git for Azure DevOps will work properly.
There will be no issues regarding stopping of ACI working when persistence or networking gets added in this new release.
The new release gives the addition of SSO support for OAuth and does not enforce a login prompt.
The new ability to manage orphaned stacks when Portainer has the compose file will help many users from now on.
Disabling of sysctl settings for non-administrators incorrectly defaults to being on will come into effect.
Now, users can adequately expose backend errors when using image management features.
This new release will now see the initial experimentation support for Podman.
From this release, we can customize the Portainer data folder in the Dev script.
Learn here about the experience between two container management tools: