IBM Cloud Kubernetes Service vs. Mirantis Kubernetes Engine

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.

Incentivized

[Mirantis Cloud Native Suite (Docker Enterprise)] is the most advanced tool till now, which works as a VMs
and separates any single application from the dependencies. Also, this tool is
helping me in the agile development of the processes. It is strongly recommended to
almost all major organizations.

Incentivized

• 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.

Incentivized

• Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
• Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
• CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.

Incentivized

• 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

Incentivized

• Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
• Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
• Networking is complexified due to internal port mapping between containers, etc.

Incentivized

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.

Incentivized

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.

Incentivized

Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.

Incentivized

IBM's cloud is almost infallible.

Incentivized

IBM's cloud has a site in my conuntry (MEXICO) so the network latency was almost 0

Incentivized

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)

Incentivized

The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.

Incentivized

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.

Incentivized

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.

Incentivized

The IBM Cloud Kubernetes Service is quite flexible platform with profitable Cloud functions performance and the data security through IBM Cloud Kubernetes Service is nice. To manage container easily and process huge amount of data at the same time, the IBM Cloud Kubernetes Service is amazing ad the platform deployment is very easy after training.

Incentivized

We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP). Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being sure that the environment is exactly the same makes things easier for developing.

Incentivized

IBM's CKS does not offers automatic autoscaling nor vertical scaling (automatic). Other services like Google Kubernetes Engine scales up and down very well

Incentivized

• 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.

Incentivized

• Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams.
• Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams
• Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization.

Incentivized