Portainer shifts to Kubernetes-first architecture with version 3.0

Portainer is shifting its development strategy with the upcoming release of Portainer 3.0, which will adopt a ‘Kubernetes-first’ codebase. This transition marks a departure from the previous model of maintaining a single codebase for Docker, Swarm, Podman, and Kubernetes. The company stated that the growing gap between these technologies makes maintaining feature parity across all of them impractical.

Under the new architecture, new features—specifically regarding policy management, operations APIs, authentication, GitOps, and observability—will primarily focus on Kubernetes. While Docker, Swarm, and Podman environments can still be managed within Portainer 3.x, they will be treated as secondary and may not receive every new platform feature.

CEO Neil Cresswell announced that the Community Edition (CE) will not be based on the 3.0 rebuild. Instead, CE will continue to be based on Portainer 2.45 LTS, the final release in the 2.x series. While CE will receive security updates and certain backported features, it will not include the new consoles or the ground-up architecture of the 3.x series. To assist users transitioning from Docker to Kubernetes, Portainer is offering the Portainer-D2K compatibility layer, which allows familiar tools like Docker Compose to manage workloads on Kubernetes clusters.