IBM Cloud Private is a Kubernetes-based container platform allowing users to build cloud-native applications on their own infrastructure. In addition, it offers common services for self-service deployment, monitoring, logging and security, as well as middleware, data and analytics.
N/A
Kubernetes
Score 8.9 out of 10
N/A
Kubernetes is an open-source container cluster manager.
N/A
Pricing
IBM Cloud Private
Kubernetes
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM Cloud Private
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 Private
Kubernetes
Features
IBM Cloud Private
Kubernetes
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
IBM Cloud Private
9.7
5 Ratings
22% above category average
Kubernetes
-
Ratings
Ease of building user interfaces
10.03 Ratings
00 Ratings
Scalability
10.05 Ratings
00 Ratings
Platform management overhead
10.04 Ratings
00 Ratings
Workflow engine capability
10.04 Ratings
00 Ratings
Platform access control
9.04 Ratings
00 Ratings
Services-enabled integration
9.04 Ratings
00 Ratings
Development environment creation
10.04 Ratings
00 Ratings
Development environment replication
10.04 Ratings
00 Ratings
Issue monitoring and notification
9.04 Ratings
00 Ratings
Issue recovery
10.03 Ratings
00 Ratings
Upgrades and platform fixes
10.03 Ratings
00 Ratings
Container Management
Comparison of Container Management features of Product A and Product B
IBM Cloud Private is an ideal platform for companies to accelerate their business growth. It helps in reducing the cost of IT and operations while delivering a great customer experience. With IBM Cloud Private, you can gain agility and security with a flexible hybrid model that fits your needs. It's highly recommended to my colleagues from me.
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.
Capacity On Demand to scale up and down environments
SaaS model allows our team to have less involvement in managing or controlling the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities.
SaaS model allows our team to worry less about upgrades, fix packs, environment support etc.
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
With VMware cloud, each VMware Cloud customer must have an SDDC account(VMC) as well as a general AWS account. The two accounts must be linked for the service to work which is a tiresome thing to do for some clients but with IBM Cloud Private all these issues are solved.
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.