IBM Cloud Kubernetes Service is a good way to start
Use Cases and Deployment Scope
Pros
- Offering a useful pre-configurated baseline
- For example offering an IBM managed ingressClass (k8s nginx, in the future traefik)
- Services as key protect (for encryption at rest), block storage etc. integrate seamlessly
- Providing a tool landscape that als integrates well and giving you most you need to start
Cons
- The possibilty to configure details is limited e.g. Azure offers the option to pause clusters or having auto updates regarding the version etc.
- Autoscaler wise, IBM has a solution but to my understanding that is also limited is not comparable to for example Karpenter (available for azure)
- Or another example, networkwise calico is available but no cilium etc.
- The whole thing is not lightwith (features that come with the IKS) respecively you cannot select a lite version (so if you do not needed this is a drawback)
- In addition to this point, it takes some time (~45 min) until your IKS cluster is ready to use
- Not IKS specific, but the amount of datacenters/locations is limited too
- The price politics, do not offer advanced possibilities to book a service for several years and save money
Return on Investment
- In general K8s eases operation at scale (together with using their tool landescape offering) and IKS is no different here
- No need to take care of self "managed" ingress class is a cost/time gain
- The complexity of K8s is in the beginning no immediate gain but depending on you use-case if can be worth it




