AWS vs Kubernetes: The New Windows vs Linux Analogy

Author: Ian Miell – open‑source programmer, speaker, writer and blogger.

For those over forty working in IT, the memory of everyone using Windows while a small but growing group compiled Linux in their spare time is still vivid.

Windows users often wonder why anyone would abandon a fully supported, easy‑to‑use OS, but reasons range from hobbyist tinkering to cost, control, speed, or simply the desire for a free operating system.

Today, the author finds himself wrestling with a new Kubernetes add‑on that behaves much like the early, confusing Linux experience: APIs changing, poor documentation, and the hallmarks of an immature large‑scale project.

Knative’s first rule: you can’t explain what Knative actually is.

Similarly, AWS colleagues ask why one would go beyond the built‑in, well‑supported services when AWS already provides everything needed.

AWS is Windows

Like Windows, AWS is a product: not highly flexible but reliable, with well‑defined APIs and solid KPIs, suitable for most real‑world workloads, yet it imposes limits on what can be achieved.

Many organizations prefer building their own data centers for cost, control, and performance, much like preferring a car you can maintain yourself rather than a mass‑produced one.

Just as Microsoft once embraced and extended Linux, AWS now embraces and extends Kubernetes, integrating tightly with AWS IAM, which is the true source of vendor lock‑in.

EKS and lock‑in

EKS, like all AWS services, is deeply integrated with IAM, making identity management changes extremely difficult for enterprises.

Changing core security systems offers little short‑term benefit and carries high risk, discouraging CTOs from pursuing such moves.

Large enterprises also consider the cost of private data centers versus cloud, with factors like expertise, asset depreciation, and data scale influencing decisions.

Running Kubernetes incurs high zero‑day costs that grow exponentially with scale, allowing AWS to profit as customers expand, often without realizing the non‑linear cost increase.

AWS and “What if Bezos loses his mind?”

Major companies funded Kubernetes’s early development (Google and Red Hat), and only when enterprises care about AWS’s monopoly will real progress be made.

If enough organizations adopt multi‑cloud strategies, AWS’s dominance could be challenged.

Linux’s open‑source model allowed many distribution choices; similarly, Kubernetes offers a “distribution” model (e.g., OpenShift/OKD) that avoids being a mere fork.

Future

Kubernetes must remain large and independent to survive, and the Cloud Native Computing Foundation’s ecosystem reflects a diverse set of technologies at varying maturity levels.

Conclusion

The core argument is that AWS to Kubernetes is like Windows to Linux; to avoid repeating OpenStack’s fate, the industry should quickly adopt robust distribution‑based management solutions for Kubernetes.

Original source: https://zwischenzugs.com/2019/03/25/aws-vs-k8s-is-the-new-windows-vs-linux/amp/