Port(ainer)ing you containers
Overall Satisfaction with Portainer
Portainer is currently used to manage our Docker Swarm environment where we are running multiple in-house and customer services. Portainer has taken the headache out of managing Docker updates by immediately showing you which containers are out of date and giving you a seamless updating capability. Scaling and HA with Docker Swarm is made so much simpler with Portainer, and showing us the environment status through a single pane of glass is cutting down on time spent to know what is going on in the environment.
Pros
- Docker Swarm Management
- Image updates
- Integration with GitLab container registry
- LDAP integration
- Service deployments and service webhooks
- Full scale Kubernetes cluster deployment and management
Cons
- The API is hard to understand and you need to often "chain" API calls
- Saved time
- Lowered the entry barrier into container and container-management
None, really. All searches pointed to Portainer every time.
Do you think Portainer delivers good value for the price?
Yes
Are you happy with Portainer's feature set?
Yes
Did Portainer live up to sales and marketing promises?
Yes
Did implementation of Portainer go as expected?
Yes
Would you buy Portainer again?
Yes
Portainer Feature Ratings
Using Portainer
3 - Development and customer service deployment and support.
- Deploying customer services in HA/clustered modes.
- Quick time to repair
- Building a development environment that devs can do rapid deployments and testing on
- None as of yet
- Deploy it for larger customers on site to manage Kubernetes clusters with.
Evaluating Portainer and Competitors
- Integration with Other Systems
- Ease of Use
I would not really changed it. A lot of reading on real-world users (sysadmins and devs alike) pointed to Portainer being the best fit.
Portainer Implementation
- Implemented in-house
Change management was a minor issue with the implementation - When documented properly, users will find it very easy to use, even with integrated pipelines.
Portainer Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved No escalation required Support understands my problem Support cares about my success Quick Initial Response | None |
Yes. Because I wanted to have peace of mind in case I ran into weird issues.
Yes. We had an issue with how locally hosted GitLab shows images from the registry. We had one call to explain the issue, the engineers asked for a bit of time to investigate fully, came back 2 days later with a work-around and a week later gave us feedback on the internal discussions they had regarding our problem.
Using Portainer
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Updating Containers to latest images
- Deploying Stacks using stack templates
- LDAP integration
- Creating Services with Webhooks
- Creating groups (especially when using LDAP)
Yes, but I don't use it
Comments
Please log in to join the conversation