Kubernetes Isn’t Getting Simpler—The Ecosystem Around It Is Getting Smarter
KubeCon always surfaces the same truth: Kubernetes may be everywhere, but running it well is still a craft. Andy Suderman, who has been deep in infrastructure work since long before Kubernetes had its first logo, traces his path from early-days cluster tinkering to leading engineering efforts at Fairwinds.
Suderman discusses the ongoing gap between what Kubernetes promises and what most teams can actually operate. Fairwinds has lived in that gap long enough to build widely used open source tools like Goldilocks and Pluto, created not as marketing artifacts but as survival gear for dealing with real cluster problems. Suderman’s examples make the point clearly: deprecations, right-sizing resources, API churn—none of these headaches disappear just because cloud-native tooling matures.
They then shift to a bigger story playing out across the industry: platform engineering finally going mainstream. AWS is pushing hard on a blueprint for internal developer platforms built from open source components—Argo, Backstage, Crossplane—and Fairwinds is one of the partners helping turn that blueprint into something teams can actually use. Suderman cuts to the chase: off-the-shelf platforms rarely fit, fully DIY platforms rarely ship, so the future is going to look a lot like tailored scaffolding assembled around open source.
The through-line is simple: Kubernetes keeps moving, tooling keeps expanding, but teams still need help turning that into reliable, day-to-day operations. Suderman makes the case that the next wave of cloud-native success will depend on that blend of open source, customization, and guidance.
