This article seems mostly content-free. It alleges (correctly, imo) that k8s implies far more operational complexity and degrees of freedom than most orgs need. This becomes especially true when orgs adopt cloud-specific features or patterns that hinder the vendor-agnosticism that they (the orgs) to provide.

However, this article is entirely absent of any helpful degree of detail as to what alternatives do or should exist. They gesture at some cloud (or other?) providers wrapping and abstracting k8s. They assert that orgs do indeed find that appealing. It’s unclear to what extent that’s true in reality, and it’s unclear what paths are available to most orgs. This article really doesn’t provide any insight for someone who has already realized that k8s has steep costs for the supposed benefit of vendor-agnosticism that gets more or less invalidated for the many orgs that also use non-portable cloud features.