Created from information via Stackrox EKS vs GKE vs AKS
I will be basing my assessment purely out of an easy of use lens. As I have not used Kubernetes before, I would like to go with the abstraction that is easiest for me to use.
I kept my evaluation criteria simple for the sake of simplicity and limited it to Price, Supported Containers, Version maturity, Logging, and release date.
| Price | Pay as you go with optional SLA add-on |
|---|---|
| Supported Containers | Docker, containerd |
| Version Maturity | Supports up to 1.20 |
| Logging | Logs are transmitted to Azure Monitor |
| Release Date | June 2018 |
| Price | $0.10/hour with optional SLA add-on |
|---|---|
| Supported Containers | Docker, containered, gVisor |
| Version Maturity | 1.17 |
| Logging | Logs are transmitted to Google Cloud’s Operarations suite |
| Release Date | August 2015 |
It is difficult to assess price without actually looking at a concrete case for these abstractions. That said, I would certainly opt for the SLA add-on. Otherwise, why would I even consider offloading the responsibility to the provider?
I chose this one because I was interested to see what each abstraction supported. I have only worked in Docker and have only touched Containered in a personal project. it is more suited for volume-less jobs. I have never used gVisor (or even heard of it.)
Unlike most kernels, gVisor does not assume or require a fixed set of physical resources; instead, it leverages existing host kernel functionality and runs as a normal process. In other words, gVisor implements Linux by way of Linux. -Gvisor’s github README
How poetic.