IBM Cloud Kubernetes Service is a
managed Kubernetes offering, delivering user tools and built-in security for rapid delivery of applications
that users can bind to cloud services related to IBM Watson®, IoT, DevOps
and data analytics. As a certified K8s provider, IBM Cloud Kubernetes
Service provides intelligent scheduling, self-healing, horizontal
scaling, service discovery and load balancing, automated rollouts and
rollbacks, and secret and configuration management. The Kubernetes…
N/A
Portainer
Score 9.6 out of 10
N/A
Portainer is a centralized container management platform for containerized apps and IoT device management. It helps accelerate container adoption and reduce time-to-value on Kubernetes, Docker, and Swarm with a management portal, allowing users to deliver and manage containerized applications from the data center to the edge. Portainer helps - Reduce the operational complexity associated with multi-cluster management Bridge the skills gap and facilitate feature…
I have earlier used various services, such as Kubernetes and Google Cloud Run. Still, IBM Cloud Kubernetes Service offers more convenience and a larger set of functions and features are available in Kubernetes. Google Cloud Run is much closer to a server less approach to …
Both services are very similar and work in a very similar way, both fulfilling their purpose well. IBM Cloud Kubernetes Service was chosen to test how a different platform from the traditional one would work during the execution of the project and whether it would perform well. …
It is more focous on enterprise security and hybrid cloud support, It is also openshift to enhance from anywhere, tight integration with other tool, It's cloud features so that we can easily to use from anywhere and it is easily to integrate with ibm other tool so that multiple …
Many solutions and vendors are offering the service to deploy a solution for based Kubernetes cloud, but we have selected IBM Cloud Kubernetes Service for the optimization, high availability, DRP process, reduced downtimes, support, documentation, and the easy way to deploy …
IBM Kubernetes Service and Azure Kubernetes Service (AKS) are two popular managed Kubernetes offerings that allow organizations to deploy, manage and scale their containerized applications.
IBM Cloud Kubernetes Service is a scalable solution, but compared to AWS and Mirantis it is not auto-scaling, and The technical support from IBM is kind of poor.
Well, as we were in a state to compulsory implement this service, but then it is very suited for deployment of a service that has higher fault tolerance. And maintaining the lifecycle of custom made resources. And the ability to integrate other services also
The agility of Kubernetes allows it to be deployed quickly with short iterations. Operability makes it work well over time, not just at [the] deployment phase and the application itself is able to expose a health check in order for the infrastructure it is running on to query …
All of the container management systems we evaluated are popular and each has its unique features and benefits. Kubernetes is the solution we found with containerization, agile development, and continuous delivery which would shorten the time it took to get a project up and …
With the scalability, the management, the coordination, IBM Cloud Kubernetes Service really empowers the whole IT team and gives the company more time back than we had before. It is a system that has the capability to manage where workloads are being distributed out and [do] …
Kubernetes was original formed by Google. We had a lot of compute in Google Cloud Platform and used to use their managed Kubernetes service Google Kubernetes Engine (GKE) and it performed quite well. I think both products are solid, but I lean toward GKE. However, I would opt …
Directing administrations, similar to API entryways, constrained you to do everything automatically through config records. I would have favored a GUI for minor design changes. I think the planned maxim was that you could push configs from versional sources, while as yet having …
We mainly selected [IBM Cloud Kubernetes Service] because IBM fabric blockchain service is mostly compatible with it. To have all the infrastructure in a single cloud to get the best output we selected the [IBM Cloud Kubernetes Service].
Routing services, like API gateways, forced you to do everything programmatically through config files. I would have preferred a GUI for minor configuration changes. I think the intended idiom was that you could push configs from versional sources, while still having a bit of …
I used also Kubernetes on-premise installation. It permits you to install a custom Kubernetes cluster in your physical machines. The advantages are clearly the complete access to the machines via ssh and the possibility of customization. In the cons, the costs are really high …
Dyrectorio was nice but it feels unpolished Ugreen has docker management on its UGOS Pro and it seems quite nice for start but its UI is quite a bit worse then Portainer Another downside is that its GUI seems to be locked on a specific port for now
Had already more experience using Portainer and it was covering all immediate needs where scalability was not a concern. Definitely easier to use and to get started for anyone.
Portainer is open source and can be installed as a docker container. Portainer can also be used free of charge as a business edition for a limited number of installations. All you have to do is register with Portainer and receive a license key. Portainer is very easy to install …
Azure and AWS have their own issues, especially around complexity just to setup one thing that Portainer can do in 10 seconds. Octopus deploy has excellent logs, analytics and dashboard views - but the configuration is more of a hassle than Portainer. Overall for the projects …
Portainer is very simple to use for anyone who is new to docker and trying to build a server. It makes everything super easy to use because of it’s excellent UI/UX which makes it a good tool for beginners!
I wrote that earlier, I tried Docker desktop so many bugs with WSL and not free and it get sign out every login time, Tried SUSE rancher too complicated and good only for power users and whoever runs Kubernetes and very heavy. tried Dokage very simple and couldn’t do …
Portainer is, in my opinion, the most accessible and straight-forward means of entering the world of deploying and managing containers while also maintaining the ability to progress into advanced professional deployments and use.
Portainer takes the cup in terms of usability and features. It is also more useful for smaller deployments, whereas Kubernetes in our opinion and experience, could probably be more suited to certain other use cases. Portainer is also a fresh feel among all the preexisting …
Initially looked into using Rancher for container management but it is
aimed more at kubernetes deployments. I have used both at home and liked
Portainer more, especially since we are using docker standalone. From
In Kubernetes management, in my opinion I would say that Lens is superior. But if you only want to manage a few stacks, Portainer is superior because the gui offers a comprehensive way of managing all the deployed images and its versions.
Microsoft Azure, and arguably the leader in the field. The most negative point and which made us make the decision not to continue with them and to go with Portainer is the price. This is one of the most important points to consider, especially in small companies.
The reason I chose Portainer is that graphically it wins over Yacht, it has many more options to use even in the free version. You can connect more than one environment to one panel which makes it much easier to use multiple instances of Portainer and saves a lot of time.
I am using Rancher in Kubernetes environments. It was really the first product I used with it and never really had time to test out how well Portainer behaves on Kubernetes. For the exact same thing - Docker Swarm management I used Swarmpit some time ago, but I like Portainer …
Portainer is a user-friendly container management platform focused on Docker, providing a simplified graphical interface. Kubernetes (K8s) is a robust container orchestration platform that automates deployment and scaling, suitable for complex container environments. Docker is …
Portainer is a lot easier to use when compared to kubernetes. it is easy to get over whelmed by all the options in kubernetes but portainer makes it simple to build and deploy even to kubernetes.
Portainer seems to be the best when you start with small environments and can grow with them. Portainer is also good for beginners with not too much knowledge about containers. Finally the start-up with 5 nodes for free was a great benefit.
IBM Cloud Kubernetes Service is ideal for deploying modern applications on a microservices architecture -- where easy scaling and ability to update are important. IBM Cloud Kubernetes Service also handles automated deployments and load balancing very well, particularly if you're already working in the IBM Cloud ecosystem. There are applications less suited to IBM Cloud Kubernetes Service -- such as very small applications, where managing an IBM Cloud Kubernetes Service cluster would be overkill. Also, users not familiar with container organization might find IBM Cloud Kubernetes Service to be a challenge to manage effectively.
Many developers, especially lesser experienced developers, don't have a really good background in setting up containers from the command line. Portainer is invaluable to them. Giving a UI to them gives them much more confidence and allows them to learn properties and capabilities of containers under far less stress. On the flip side of this, giving then a UI on a production system can lead to chaos...never give junior developers access to production servers.
IBM has a strong focus on serverless and Kubernetes. This shows in the platform. Deploying containers to Kubernetes was very easy.
Deploying a Kubernetes cluster through the GUI is very easy and quick. On top of that, IBM Cloud offers a single node cluster for Free.
Container Registry is a very good product for managing container images. Integration with Kubernetes was seemless.
Portability. To transition from Google Cloud Kubernetes to IBM Cloud Kubernetes took almost no effort. We mostly use the CLI and the standard tools such as kubectl were present.
Separating server maintenance with application development, providing a clear user interface for developers who don't want to worry about the underlying server.
RBAC for container deployment linked to a SAML IDP, not something particularly easy in a native Docker instance but point and shoot in Portainer, allowing the use of Azure / Okta etc to provide user access.
Image management with multiple repositories is super clear and reduces incidents
I constantly get this error even when everything is well configured prefect.exceptions.AuthorizationError: [{'path': ['auth_info'], 'message': 'AuthenticationError: Forbidden', 'extensions': {'code': 'UNAUTHENTICATED'}}]
Then sometimes the error disapear without changine anything, happened twice to me. Should there be an issue with the authentication service? Please let's improve or let users know why this may be happening.
Improve the UX in the browse console when removing many images at once
UX on the process of installing KeyCloack operator
Lack of granular RBAC control: While Portainer does have role-based access control (RBAC) features, they are not as granular as some users would like. Some users have reported that they would like to have more control over permissions for individual users or groups. This would enable more fine-grained control over who has access to which containers or clusters.
Limited support for non-Docker container technologies: While Portainer is primarily designed to manage Docker containers, it does have some limited support for other container technologies like Kubernetes and Docker Swarm. However, this support is not as robust as it is for Docker, and some users have reported that they would like to see better support for other container technologies.
Limited control over container networking: Portainer's networking features are somewhat limited compared to other container management tools. Some users have reported that they would like more control over container networking, including the ability to create custom networks and control IP addresses.
We have our application running on a CentOS compartment on IBM Cloud Kubernetes Service. We have been utilizing the help since IBM Cloud initially dispatched. We liked the adaptability and versatility that IBM Cloud Kubernetes Service give us. Since we are tiny, the Kubernetes administration is just utilized at present inside my venture bunch.
We actually haven't had any real problems in our clusters recently and the results we have gotten from adopting IBM Cloud Kubernetes Service have been beyond even our greatest expectations. The community has helped optimize the use of the system and make it relatively simpler to use.
Accessibility for Non-Experts: even with some people having a bit longer on-boarding it is still very simple Quick setup is insanely useful, we can get it running in 10 seconds after installing docker Portainer has once again super clean UI and is very user friendly. Deployment/monitoring and management are super easy. I can tell just from a glance if something is out of date (watching at you Watchtower not doing your job for some reason)
The self-guided support was solid, and there are plenty of online videos to guide first time users, but I think one area of improvement is a faster way to transfer a large quantity of files from our local machine to the cloud for storage (Aspera)
One of their staff members jumped on a video call immediately with me and led me through the problem and solution during a quick session of screen sharing. In this day and age that is above and beyond, especially when it comes to software. It took approximately 5-10 minutes to diagnose and fix, including pleasantries!
Online training is really an important resource for using these tools. IBM's help center is rich in useful information and tips. Also, external guides and tutorials are available (e.g. on youtube), but I followed only IBM ones and I had no difficulties.
Ease of use. Very intuitive. We have been looking for a product that allows us to orchestrate our docker containers in a way where it allows us to effectively scale our applications to production. It also provides us a way of monitoring all our infrastructure in a very clear concise way.
I have earlier used various services, such as Kubernetes and Google Cloud Run. Still, IBM Cloud Kubernetes Service offers more convenience and a larger set of functions and features are available in Kubernetes. Google Cloud Run is much closer to a server less approach to deployment, although it gives slightly less flexibility in terms of configuration than IBM Cloud Kubernetes Service.
Portainer takes the cup in terms of usability and features. It is also more useful for smaller deployments, whereas Kubernetes in our opinion and experience, could probably be more suited to certain other use cases. Portainer is also a fresh feel among all the preexisting container management solutions and brings positivity and a new breeze in the industry.
IBM's CKS does not offers automatic autoscaling nor vertical scaling (automatic). Other services like Google Kubernetes Engine scales up and down very well
IKS can provide around 30% savings when it comes to operational costs since Kubernetes is designed to run applications in most machines in the most efficient manner possible.
Managed Kubernetes can save a company time by 45% since Managed Kubernetes usually is seamlessly updated, without any interruptions with the workload. IKS fall into this benefit.
We heard people had saved in maintenance downtimes when it comes to Kubernetes by a factor of 10 so IKS can contribute to more flexible and distributed services with virtually no downtime.
Instead of having 1 senior who does all the setup, debugging and caretaking of "all things docker" we now split the load on basically everyone in the team. Hard to put into direct numbers but with everyone helping themselves, noone alone is forced into that position "because you know how to do it" and overall we're more productive