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 9.3 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
Ratings
0% above category average
Kubernetes
-
Ratings
Ease of building user interfaces
6.90 Ratings
00 Ratings
Scalability
7.90 Ratings
00 Ratings
Platform management overhead
7.80 Ratings
00 Ratings
Workflow engine capability
8.00 Ratings
00 Ratings
Platform access control
8.70 Ratings
00 Ratings
Services-enabled integration
8.60 Ratings
00 Ratings
Development environment creation
8.00 Ratings
00 Ratings
Development environment replication
8.00 Ratings
00 Ratings
Issue monitoring and notification
8.00 Ratings
00 Ratings
Issue recovery
8.90 Ratings
00 Ratings
Upgrades and platform fixes
7.20 Ratings
00 Ratings
Container Management
Comparison of Container Management features of Product A and Product B
It is a perfect application when you have multiple users and/or developers and you want to create rules and standards for access and the ability to change access levels. The reporting of usage is good, but adding more granularity into the metrics that have been used to measure are not specific enough. They provide detail but drilling into the detail would be more appropriate i.e. access to the baseline data.
Along with all the best features and support by k8s, the automatic container scheduling to worker nodes and also self-healing containers which is what I like the most. On the other side, when I was installing the k8s cluster on CentOS 8, it was quite difficult for me, but never mind it is working as we expected and it is a one-time effort. Especially, in my case, there are more than 7 application containers required to run and communicate with each other, so for us, Kubernetes is an optimal solution.
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
1) One-stop solution for all the complex network connectivity managed by [IBM Cloud Managed Istio]. 2) Nice dashboard to understand the flow. 3) Easy to troubleshoot the service if any one of the APIs is not responding. 4) We can integrate it with Azure Kubernetes service and other cloud provider Kubernetes services. 5) Monitoring the health of the pods can be easily configured and alerts can be triggered very accurately with this tool.
As I said earlier also - - K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability. - K8s is not limited to only a single networking or storage solution as compared to OpenStack. - Networking (which is a key concept) is much simpler in K8s as compared to OpenStack. - It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.