The Great Power of Kube on IBM Cloud
December 02, 2022
The Great Power of Kube on IBM Cloud
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with IBM Cloud Kubernetes Service
My team and I utilizes this service to deploy our core IAAS services to host platform services as well as core infrastructure services that provide customers with access to computer, network, and storage resources. Kubernetes is used as the main orchestration layer for our services through the use of ingresses, Kubernetes DNS service, and various K8s resource types such as deployments, stateful sets and daemon sets. Additionally, Etcd is used to maintain the life cycle and state of customer resources such as virtual machines, vpcs, subnets, volumes, etc ...
- Provide an underlying infrastructure layer for cloud services and a means for them to easily communicate with one another via apis
- Provide a means to manage the lifecycle of events through Etcd to reach desired states for cloud resources
- Provide a means to easily rollback and upgrade services with no downtime
- Providing a means to deploy services across Kubernetes clusters (multi-region)
- Easily monitor services without external services (my team is currently using sysdig)
- CLI needs to be more easily usable and have more short cuts to make commonly done tasks more easily accessible without typing much
- Better online video demos of how to perform tasks in the Service
- The service has saved our team several hours creating, managing, and maintaining
- our own orchestration system and has allowed our sub-teams to focus on delivering
- more core features to customers.
- From a dependency perspective, it is a negative impact as IBM Cloud Kubernetes
- service is looking to deploy their service on our infrastructure thus forcing our team
- to deploy Kubernetes on bare metal nodes.
My organization has significantly benefited from the use of the CLI and API, not so much the GUI. It has made it easily especially for operations engineers to easily automate tasks via scripting existing CLI and API commands. Our CI/CD team was able of taking advantage of APIs to create build and deploy pipelines for our clusters.
Sysdig and LogDNA are the two main third-party services my team utilizes along with IBM Cloud Kubernetes Service. They are exclusively used for monitoring/diagnostics and logging respectively as current IBM Cloud Kubernetes Service capabilities for these features out of the box don't provide the necessary features we need. Sysdig is capable of providing a high degree of accuracy to monitor the state and other metrics of services hosted in our cluster as well as providing helpful dashboard to visualize the data. LogDNA provides our team with an easy way to query logs efficiently.
- IBM Cloud Activity Tracker
Activity Tracker is another third-party service my team utilizes along with IBM Cloud Kubernetes Service. It is exclusively used for tracking key events within our service operations such as CRUD operations for resources or resource state transitions and has been crucial in tracing main customer actions as they interact with our product.
Do you think IBM Cloud Kubernetes Service delivers good value for the price?
Yes
Are you happy with IBM Cloud Kubernetes Service's feature set?
Yes
Did IBM Cloud Kubernetes Service live up to sales and marketing promises?
Yes
Did implementation of IBM Cloud Kubernetes Service go as expected?
Yes
Would you buy IBM Cloud Kubernetes Service again?
Yes