Sourav Rudra reports that Portainer’s decade-old Community Edition has hit a wall: the ground-up, Kubernetes-first Portainer 3.0 will not be the base for CE, which stays on the 2.45 LTS 2.x line and receives only security fixes, bug fixes, and 3.x backports where a matching Docker API exists, with no guarantee of feature parity because some 3.x capabilities depend on Kubernetes primitives. CEO Neil Cresswell calls it a maintenance problem rather than a strategy pivot, saying policy and API work had to be built three times for Kubernetes, Swarm, and Docker/Podman, and that releasing the enterprise-oriented 3.x consoles as CE would misrepresent them. The only no-cost route onto 3.x is the closed-source Business Edition’s 3 Nodes Free license, and the article points to Komodo and BSD-3-Clause Arcane as alternatives for users unwilling to stay on 2.x.
Portainer freezes Community Edition at 2.x as 3.0 goes closed-source and Kubernetes-first
Sourav Rudra reports that Portainer's decade-old Community Edition has hit a wall: the ground-up, Kubernetes-first Portainer 3.0 will not be the base for CE, which stays on the 2.45 LTS 2.x line and receives only security fixes, bug fixes, and 3.x backports where a matching Docker API exists, with no guarantee of feature parity because some 3.x capabilities depend on Kubernetes primitives. CEO Neil Cresswell calls it a maintenance problem rather than a strategy pivot, saying policy and API work had to be built three times for Kubernetes, Swarm, and Docker/Podman, and that releasing the enterprise-oriented 3.x consoles as CE would misrepresent them. The only no-cost route onto 3.x is the closed-source Business Edition's 3 Nodes Free license, and the article points to Komodo and BSD-3-Clause Arcane as alternatives for users unwilling to stay on 2.x.
Source: It's FOSS