The IBM Cloud Kubernetes Service provides the Managed Istio installation add on, designed to provide additonal control over clusters and the microservices they comprise via automatic updates and lifecycle management of control plane components, and integration with platform logging and monitoring tools.
N/A
Kubernetes
Score 8.9 out of 10
N/A
Kubernetes is an open-source container cluster manager.
N/A
Pricing
IBM Cloud Managed Istio
Kubernetes
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM Cloud Managed Istio
Kubernetes
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Cloud Managed Istio
Kubernetes
Features
IBM Cloud Managed Istio
Kubernetes
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
IBM Cloud Managed Istio
8.0
5 Ratings
3% above category average
Kubernetes
-
Ratings
Ease of building user interfaces
6.95 Ratings
00 Ratings
Scalability
7.95 Ratings
00 Ratings
Platform management overhead
7.85 Ratings
00 Ratings
Workflow engine capability
8.05 Ratings
00 Ratings
Platform access control
8.75 Ratings
00 Ratings
Services-enabled integration
8.65 Ratings
00 Ratings
Development environment creation
8.05 Ratings
00 Ratings
Development environment replication
8.05 Ratings
00 Ratings
Issue monitoring and notification
8.05 Ratings
00 Ratings
Issue recovery
8.95 Ratings
00 Ratings
Upgrades and platform fixes
7.25 Ratings
00 Ratings
Container Management
Comparison of Container Management features of Product A and Product B
Clearly, the [IBM Cloud Managed Istio] tool is very useful when you have multiple services and each service is connecting with other services through APIs in different networks. To manage this type of complex network, [IBM Cloud Managed Istio] is very useful. It comes with a license that can increase the billing of your project so make sure if your application network mesh, monitoring cannot be managed on your own then you can use it. If your application is not very complex then you have many tools available like Grafana, Prometheus, Sumo Logic, which you can integrate individually with your cluster and implement. In this type of scenario, it is better to not use [IBM Cloud Managed Istio] and it will serve your purpose as well.
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.