And that is why pricing and features sit right at “good enough” and not great.
That to me is a product they offer because someone else is offering it, but they don't want you to actually use it.
If you're actually looking to build isolation in AWS then you're going to need EC2 dedicated for your EKS member hosts. So you're not getting isolation for $200/month (I'd have to spec it out but dedicated hosts are pricey to the point that it'd be competing with physical hardware in a colo).
That $200/month for not-really-isolated is also per plane. So if you want a separate staging environment it's another $200/month. Client API sandbox? Same thing. It's wack.
I'd be surprised if they have the same operational maturity, which translates to uptime, which was what I was talking about.
A quick search turns up these SLAs:
<bad link>
vs
https://cloud.google.com/blog/products/containers-kubernetes...
EKS: 3 nines
GKE: 3.5 nines
So Google is committing to 1/2 the downtime.
(Note the GKE SLA is for regional clusters, which is what you should be doing if you care about uptime. The zonal cluster SLA is 2.5 nines. I couldn't find a difference in EKS, maybe there's an equivalent better SLA for regional clusters I couldn't find.)
Edit - that EKS SLA link formatted weirdly, and so I did a little more digging and found a more recent SLA which matches GKE: https://aws.amazon.com/about-aws/whats-new/2020/03/amazon-ek...
So, per my original comment, I am surprised. (Having never used EKS directly I have no idea what their actual uptime is; in my experience GKE has been way higher than 3.5 nines, but obviously I don't have enough data to make statistically significant observations on this.)
We haven't had any issues with k8's upgrades either.