Superlatives for All
This week, we’d like to call your attention to an excellent post contributed by Karen Bruner from StackRox, where she examines what the three major cloud providers offer in the way Kubernetes services.
For us, it was perfect timing. We’ve been talking about doing a comparison of various services across the different cloud providers for awhile. It can be a challenge in that they do not lend themselves, perhaps intentionally on their part, to apples-to-apples comparisons. Different vendors have different features, different approaches to administration, different tie-ins to their own services, etc.
Bruner, for instance, pointed out that all three K8s providers are pretty comparable for recently added Kubernetes features, like Windows containers and GPUs. The major difference has to do with the administrative services each provides. It may come down to whether a business is a Microsoft shop, as we used to say, or have more engineers comfortable with the Google or AWS way of doing things.
She also notes that service limits are handled differently across providers: Limits are per account using Amazon Web Services Elastic Kubernetes Service, per subscription using Azure Kubernetes Service, and per project using the Google Cloud Engine. Interestingly, she notes that Amazon Elastic Kubernetes Service offers something the other Kubernetes providers don’t — a financially backed service-level agreement (disclosure: AWS is a sponsor of The New Stack).
With all these comparison pieces, we almost inevitably get feedback concerning other entrants that may have been included but, for time or fiscal or sanity restraints, just weren’t. Where’s IBM? DigitalOcean? Good ideas, all. But such pieces are not meant to be comprehensive, but rather provide one more point-of-view into the vastly complex world of cloud native computing. And we are always looking for more perspective along these lines, so if you have your own thoughts to share, by way of a contributed post, hit us up at email@example.com.