With the announcement of the launch of Portainer CE 2.0 on the 31st August, I‘d like to provide additional context on our thinking behind this release, the value we hope it will bring, the target audience, and what you can expect to see from it, features-wise.
So, the time has finally arrived. Portainer CE 2.0, with support for Kubernetes is finished... and it will be released to the public on Aug 31st.
Why are we so excited about this?
Well, because we have made Kubernetes so easy to use that you don't actually need to know ANYTHING about Kubernetes to use it.
Hi Portainer Fans...
As you would have no doubt already seen, we recently released Portainer 1.24.1 to address some security concerns raised by an external security professional. Full Credit to Iain Smart for reporting the findings (https://twitter.com/smarticu5).
Let me explain the changes, shown below, and why.
Over the past three years, Portainer has become a successful open source project, used all over the world by hundreds of thousands of engineers every month. The Portainer community grows at about 50% CAGR, and with our upcoming Kubernetes release, we expect to see it grow even faster.
Continuing the theme of big changes in the Portainer world, today we’re announcing that we will be releasing a commercial version of Portainer in the next couple of months.
While our detailed thinking around the commercial versions of Portainer will be posted closer to the release, I would like to take this opportunity to outline our thoughts, as this is a pivotal and often polarizing moment in any OS project history.
Over the coming weeks we will announce the availability of Portainer Community Edition 2.0. We expect to ship code mid Q3, however it’s always dangerous to announce a date too early.
But before I talk about 2.0, I want to talk a bit about prioritization and decision making.
Recently we requested your input to complete a survey on how you use Portainer, where you use, how you rate it, and which features you love... we also asked you to tell us what features we dont have that really should...
Well, after 1200 responses in 3 days (thank you, this is awesome!!) we have compiled the below info-graphic to summarize.
By now hopefully you have seen that we shipped version 1.24 of Portainer CE; this is the very last version of the 1.X series, which has carried Portainer through the last 3 years. This version will continue receive required critical security patches for the next 12 months, however there will be no new features, enhancements or bug fixes.
What a whirlwind the last 5 weeks have been... we have received a simply staggering level of feedback and support for our first beta of Portainer for Kubernetes, with over 220,000 downloads, many positive confirmations of successful deployments across a multitude of Kubernetes versions, and Kubernetes platforms, and with a really low number of reported issues.
Hi there Portainer community,
So this month we will be releasing Portainer 1.24.0, and this version is the last of our 1.XX releases, as we transition to Portainer 2.0, which will be released end of June.
As a way to "draw a line in the sand" in regards to our currently open bugs (which total approximately 107), we spent considerable time reviewing every bug, attempting to reproduce it, determining what was likely needed to fix it, and then assigning a priority and timeline for fix.