{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Why Kubernetes Outages Are Usually Human Failures, Not Platform Bugs","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/52f85802\"></iframe>","width":"100%","height":180,"duration":717,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/why-kubernetes-outages-are-usually-human-failures-not-platform-bugs.\nKubernetes failures are rarely technical. Human error, undocumented complexity, and hero engineering turn powerful platforms into fragile systems.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #kubernetes, #kubernetes-complexity, #cloud-infrastructure-failures, #kubernetes-observability, #kubernetes-blast-radius-design, #kubernetes-outages, #kubernetes-best-practices, #site-reliability-engineering,  and more.\nThis story was written by: @davidiyanu. Learn more about this writer by checking @davidiyanu's about page,\n            and for more stories, please visit hackernoon.com.\nKubernetes isn’t inherently complex—teams create fragility through undocumented tooling, hero engineering, and unchecked operational sprawl. The fix is discipline, simplification, and shared understanding.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}