> For the complete documentation index, see [llms.txt](https://docs.portainer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portainer.io/sts/whats-new.md).
# What's new in version 2.43
Portainer version 2.43 includes a number of new features, fixes and updates. For a full list of changes, please refer to our [release notes](/sts/release-notes.md).
## Short Term Support (STS)
2.43 is a Short Term Support, or "STS", release of Portainer. STS releases intended to be an introduction of new features and functionality in Portainer, and while we do perform significant testing prior to release are not recommended for production use. For production, we recommend staying with the Long Term Support (LTS) releases. The features that appear in STS releases will, once refined and stable, be implemented in the next LTS release.
You can read more about our release principles in our [lifecycle policy](https://docs.portainer.io/sts/start/lifecycle).
## New in this release
### Automated image cleanup policies 
You can now create an [image cleanup policy](/sts/admin/environments/policies/docker-policies/cleanup-policy.md) that automatically removes old and unused Docker images on a schedule, helping you reclaim disk space without manual intervention. Configure age-based or storage-threshold-triggered cleanup and protect specific images from removal.
### Native Kubernetes RBAC support 
[Kubernetes RBAC policies](/sts/admin/environments/policies/kubernetes-policies/kubernetes-rbac-policy.md) now include a native Kubernetes permission model as an additional option alongside the existing legacy Portainer privileges model. With native Kubernetes RBAC, permissions accumulate across cluster, team, and namespace roles, aligning with standard Kubernetes expectations. This is the recommended option for new deployments.
### Add KubeSolo Edge Environments directly from Portainer 
Business edition users can now [onboard KubeSolo edge environments](/sts/admin/environments/add/add-a-kubesolo-edge-environment.md) directly through the Portainer Environment Wizard.
[KubeSolo](https://kubesolo.io/) is a lightweight, single-node Kubernetes distribution built for edge deployments. The wizard generates the setup command for your environment and walks you through deploying the Portainer Edge Agent - whether you're installing KubeSolo fresh or already have it running and just need to add the agent.
### Create and edit GitOps sources directly from the Sources view  
The [GitOps source](/sts/user/app-delivery/sources.md) view is now the central place to manage your Git connections. Admin users can [create new GitOps sources](/sts/user/app-delivery/sources/add-a-new-source.md) directly from this view - replacing the previous approach of entering Git credentials individually within each workflow. Connection details, authentication settings and source access are also now editable in place.
### SSRF mitigation  
Portainer now includes built-in SSRF mitigation. A [new setting](/sts/admin/settings/general.md#ssrf) lets you define an allowlist of permitted proxy destinations and choose how Portainer responds to requests outside that list - blocking them (enforce mode), logging them (audit mode), or taking no action.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.portainer.io/sts/whats-new.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.