IBM Cloud Kubernetes Service vs. Percona Kubernetes Operators

IBM Cloud Kubernetes Service also stands out in environments where the workloads vary continuously and require befitting scale. The product excels particularly in microservices structures, wherein the companies would harness the capacity for container orchestration and automated scaling. Still, it may face the challenges due to monolith applications that have not been originally developed for using container technology.

Production ready, robust DB solution built for Kubernetes envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional" MySQL and other clustering solutions. Also be sure to match it with proper k8s storage solutions.

• 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

• Easy and fast deployment.
• A reliable, fully automated, high-available db lifecycle management solution.
• Exaustive documentation.
• Production ready.

• 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

• Some differences compared to "traditional" MySQL solution.
• Had some hard times trying to use it combined with pre-existing techs like WordPress, Magento, etc.
• The specific k8s environment features can have an impact on it, like the storage solutions offered by the cloud vendor.

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

Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. It requires a bit of learning time for people new to operators ecosystem.

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

Well documented, there was no need to contact support.

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

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

Incentivized

For a long time we struggled finding a viable solution to migrate our existing db workloads inside Kubernetes. Before "operators era" proper db workloads required manual management, of course that easily raised administrative overhead. Then the future started to be brighter with the introduction of operators and the "official" Oracle's MySQL Operator, then Presslab's one, finally Percona's operator. Compared to other operators, the last one allowed us to ship production db workloads inside k8s.

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

• Increased development speed and agility allows to build features faster and more economically.
• Improved resource utilization helps keep applications running very efficiently, which saves on cloud service expenses.
• Scalability and resilience allows for scaling up or down based on demand, which keeps applications running efficiently and more economically.

Incentivized

• It allowed us to use k8s on our entire infrastructure.
• Decreased administrative overhead around our db services.
• As it is an open source technology, it cut down our db pricings.