Readit Newsfawadkhaliq commented on A case for Operational Safety in software operations chkk.io/blog/a-case-for-o... · Posted by u/fawadkhaliq
"Operational Safety" is the neglected child of software operations. I saw how it was implemented effectively when working at AWS, but the broader software ecosystem appeared oblivious to this key concept. While the CrowdStrike outage caused havoc, its silver lining is that Operational Safety has now become a key consideration for software leaders, all the way to CIOs.
It must stay this way as complex, mission-critical systems will continue to rely more and more on software and cascaded failures are just a fact of life in these systems.
I agree that the broader software ecosystem has been slow to recognize the importance of Operational Safety. The CrowdStrike outage, while unfortunate, has indeed served as a wake-up call, elevating Operational Safety to a priority for software leaders and CIOs alike.
As you pointed out, the reliance on complex, mission-critical systems is only increasing, and cascading failures are an inherent risk we must address proactively. By learning from organizations like AWS that have successfully integrated Operational Safety into their practices, we can work towards a more resilient and reliable software ecosystem. Let's continue to advocate for making Operational Safety a foundational element in software operations across the industry.
fawadkhaliq commented on Linkerd no longer shipping open source, stable releases buoyant.io/blog/announcin... · Posted by u/rtzo
How are users handling this change? With Buoyant cutting down on their investment, does Linkerd OSS have enough contributors to sustain it?
"As of Linkerd 2.15.0, the open source project no longer publishes stable releases. Instead, the vendor community around Linkerd is responsible for supported, stable releases."
Burned by the shared responsibility model way more than we would have liked. AWS said that they will “take the muck away” back in 2011. I guess we are back to owning the muck now :)
Couldn't agree more. As someone who used to work at AWS, I've seen it from both sides. AWS has valid reasons (business and technical) for not taking responsibility for all the layers on top. The missing piece is the operational knowledge AWS possesses but platform teams elsewhere lack access to. That's one reason to bring in a “trusted broker” to bridge this gap.
Liked the concepts described here which impact every single platform team. Do you see teams abandoning k8s because of the monotonous increase in its complexity as your infrastructure grows?
k8s complexity is a challenge at scale, but its growth seems likely. Reasons include strong community/support, continuous innovation ensures new capabilities regularly added, overall standardization across various layers of substrate to name a few. It's not for everyone though. Teams with simpler needs might find k8s overkill and opt out for valid reasons. Overall, benefits + community support make it a go-to for many, despite the challenges.
fawadkhaliq commented on ClickOps is dead. Long live IaC abbey.io/blog/clickops-is... · Posted by u/jeffchao
What are the factors that lead to ClickOps not scaling? Company size? When should a company know that it’s time to move to IaC?
Dead Comment
It's just sooo hard to reconstruct the "minimum relevant context" from running infrastructure state matched against a moving target (i.e. the next version you should be upgrading to).