The latest News and Information on DevOps, CI/CD, Automation and related technologies.
As shortages of consumer goods and rising prices caused by bottlenecks in international supply networks have become more common, the global supply chain and its vulnerabilities have been top of mind for many. For developers, several high-profile software security exploits have recently underscored the risks inherent in a similar type of supplier network: the software supply chain.
There are a handful of providers that large parts of the internet rely on: Google, AWS, Fastly, Cloudflare. While these providers can boast five or even six nines of availability, they’re not perfect and - like everyone - they occasionally go down.
Ask most SREs how many incidents they’d have to respond to in a perfect world, and their answer would probably be “zero.” After all, making software and infrastructure so reliable that incidents never occur is the dream that SREs are theoretically chasing. Reducing actual incidents by as much as possible is a noble goal. However, it’s important to recognize that incidents aren’t an SRE’s number one enemy.
The first few minutes of an incident are often the hardest. Tension and adrenaline levels are high, and if you don’t have a well-documented incident management plan in place, mistakes are inevitable. It was actually the years I spent managing incidents without the right tools in those high-tension moments that inspired me to build FireHydrant. I built the tool I wished I’d had when I was trying to move fast at the start of incidents.
Helm is a deployment tool for Kubernetes objects that supports package management, dependencies, and templating. In this article, we will explore how to optimize your Helm charts. To follow along, you’ll need a basic understanding of Helm and will have ideally written and deployed some basic Helm charts.
Summer is finally here in the Northern Hemisphere and as we work on getting our collective outdoors time in, we also have been busy at work making some great enhancements to Shipa. We kicked off June with a great webinar with PeladoNerd focusing on LATAM. We continued to focus on building and enhancing Shipa.
Get ready for the future of Mattermost mobile. Beta testers can now access Mobile v2.0, including multi-server support — our most requested mobile feature ever. We’re also bringing you a number of usability enhancements and performance improvements to make you productive on the go. If you want to be on the cutting-edge of Mattermost mobile development, we’d encourage you to join the mobile beta program today.
