IKS: Early adopter but needs some polish
November 26, 2019
IKS: Early adopter but needs some polish

Score 5 out of 10
Vetted Review
Verified User
Overall Satisfaction with IBM Cloud Kubernetes Service
I'm currently trialing out IBM Cloud Kubernetes Service as part of my independent testing since our platform uses Kubernetes as our primary deployment method for our PaaS.
Pros
- Automated Kubernetes setup
- Upstream Kubernetes
- Has the option of having bare-metal instances
Cons
- Currently, the pricing for the instances is quite high (30% higher than major vendors), so that needs to be worked on.
- VM spinup times are slower than most major cloud vendors, if GCP only takes 60 seconds on average, IBM Cloud takes more than 10 minutes. This should be faster and could use more improvement
- While providing a barebones dashboard for Kubernetes is great, I believe having the IKS service to have its own managed dashboard is better than providing the upstream Kube's dashboard.
- IKS can provide around 30% savings when it comes to operational costs since Kubernetes is designed to run applications in most machines in the most efficient manner possible.
- Managed Kubernetes can save a company time by 45% since Managed Kubernetes usually is seamlessly updated, without any interruptions with the workload. IKS fall into this benefit.
- We heard people had saved in maintenance downtimes when it comes to Kubernetes by a factor of 10 so IKS can contribute to more flexible and distributed services with virtually no downtime.
I don't think we've benefited since the management of the IKS clusters still requires us to be in the Kubernetes dashboard: again, most vendors usually have their own management dashboards, without relying on the upstream dashboard, so this is a kind of a problem when we want to interact via Web UI. This needs to be worked on.
Allowing the use of third-party services is a good thing since most enterprises can mix and match solutions. In our case, we might need app A to interact with the Watson service, that's possible because IKS has integration for it without doing anything, however, there must be quality control when it comes to add-ons since not all of them are beneficial in Kubernetes' scope.
I say IKS still has a more to work, while it benefits in being an early adopter like GKE, most of these services are easier to work on when it comes to web management, something the IKS lacks and needs to improve since its release because of how well-established the management flow works on these platforms.
Comments
Please log in to join the conversation