IBM Cloud Kubernetes Service Review
Overall Satisfaction with IBM Cloud Kubernetes Service
We use IBM Cloud Kubernetes Service for research purposes. It is used by the whole Cloud services research team. It allows us to scale up easily our applications and to set up autoscale mechanisms when a condition is verified. We use IBM Cloud Kubernetes Service because it is really cost-effective and permits a precise billing based on the used resources.
Pros
- Cost effective
- Horizontal Scaling
- Microservice Approach
- Containerization
Cons
- Overkill for simple applications
- Learning curve slow
- Not all software are native compatible
- You can scale up horizontally by adding low-cost nodes to your cluster.
- Once configured, it requires really simple configurations for new worker nodes.
- The switching phase is not trivial, and sometimes requires additional NFS storage for sharing volumes.
In our experience, we typically use IBM Cloud Kubernetes from CLI. It is really powerful and permits us to manage the entire cluster with simple APIs. CLI tools can be installed also on dumb terminals so that no powerful and GUI furnished nodes are required for managing the Cluster. Sometimes we use also the web GUI, really intuitive and complete, but less flexible than CLI.
We have deployed only custom applications on IBM Cloud Kubernetes Service.
I used also Kubernetes on-premise installation. It permits you to install a custom Kubernetes cluster in your physical machines. The advantages are clearly the complete access to the machines via ssh and the possibility of customization. In the cons, the costs are really high for maintaining an entire infrastructure by yourself. For our purposes, in the end, we chose IBM Cloud Kubernetes Service, totally managed by IBM.
- IBM Cloud Container Registry
I use IBM Cloud Container Registry for storage and sharing of my custom container images.
- Online training
Comments
Please log in to join the conversation