1. Eliminate internal Kubernetes management platform
"We had five developers working on an internal Kubernetes platform for roughly 2 years. They were building in-house applications to provide a UI and all of that.”
Portainer replaced the need for this platform.
This represents a significant cost saving, as two years of work from 5 developers likely cost $1.7 million dollars.
2. Improved accessibility and usability
”We originally started with Portainer because people wanted something to have a quick glimpse of what’s going on.”
This highlights how Portainer provided an easy-to- use interface for monitoring.
“Most devs are not comfortable on the CLI, and it’s much more difficult to look when you scale up to 50, 5 or 10 is fine, but the command line isn’t that great when it comes to managing 50 or more nodes.”
This quote demonstrates how Portainer’s UI became increasingly valuable as they scaled up their container usage.
The interviewee estimated that about 500 people in the organization were exposed to Docker and Portainer, including IS (Information Systems) personnel.
3. Enhanced security and compliance
"I think people are really happy about RBAC. That was the biggest reason why we bought Portainer."
This quote emphasizes the importance of Role-Based Access Control for their organization.
“Now we have the Sox Compliance to adhere to so we need to control what the developer is able to modify, and the other guys to be able to troubleshoot. So that really solved the big issue that we’ve had for such a long time.”
This quote highlights how Portainer’s RBAC features helped with SOX compliance and segregation of duties.
4. Streamlined operations
”Everyone knows now. We put portainer.ourdomain. Everyone’s going to the right one. There’s no confusion.”
This shows how consolidating to a single access point simplified their operations.
"We had 15 to 20 swarm clusters which was less than ideal. Now everyone knows where to go. We put portainer.ourdomain. Everyone’s going to the right one. There’s no confusion."
This shows how consolidating to a single control plane simplified their operations.
The interviewee mentioned they had “15 to 20 swarm clusters” and even more Portainer instances when counting dev environments. Consolidating these into a single point of access was a significant improvement.
5. Increased productivity
While the interviewee couldn't directly confirm this, they acknowledged the potential:
"Yeah, just for the team to look at this image and single pane of view for the network. That’s really helpful.”
