#Puppet Playbook Runner. One platform. Zero compromise. #DevOpsTools #ToolConsolidation
Struggling to manage automation across too many tools? Puppet Edge Playbook Runner lets you reuse the you already rely on...without rewriting a thing.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Top 10 Rancher alternatives in 2026: Beyond cluster management
Looking for Rancher alternatives? Compare the top 10 Kubernetes Management Platforms for 2026. From Qovery to OpenShift, find the best tool to scale multi-cluster operations and reduce TCO.
To change your engineering culture, start by asking your team what sucks
Most engineering leaders have a very known and very annoying "normal error." It's the log entry or deployment glitch that has been around so long that it is simply accepted as part of the status quo. Jeff Schnitter, a Solution Architect at Cortex, describes this as a form of organizational Stockholm syndrome. This mindset is unsustainable for several reasons.
What is DevOps?
Learn what DevOps is from a founder of the movement, Co-founder of DevOpsDays, O11y, and Inuits, FOSS advocate: Kris Buytaert.
What does an on-call responder do
An on-call responder is the first line of defence when something breaks. They assess the situation and take appropriate action. This guide walks you through what that actually looks like. You’ll see how on-call responders think through an incident and figure out what needs to be done.
Who should be on-call
There usually isn’t a hard and fast rule about who should be on-call. Teams often look for criteria like seniority, experience, or expertise. While those factors certainly help, they might matter less than you think. It is often more useful to look at whether your processes are ready. When incident responses rely on memory and intuition rather than documentation, even experienced engineers can struggle. They might handle things through internal knowledge that isn’t available to everyone else.
Introducing Megaport On-ramp as a Service
Megaport On-ramp as a Service is the fastest way for service providers to offer secure, private connectivity to mission-critical applications, and it’s now available. Considered the gold standard, private connectivity is the superior way to reach enterprise applications, storage services, or security services. But for most service providers, offering a private on-ramp for customers to connect to isn’t straightforward.
What it takes to build and scale developer platforms | Canonical x Qualcomm
Ubuntu on @qualcomm platforms simplifies access to Qualcomm’s advanced AI accelerators and capabilities, empowering developers and enterprises to innovate with confidence. Learn about the work we’re doing to bring Ubuntu to Arduino and other Qualcomm-powered boards. The Qualcomm and Canonical partnership provides developers with a reliable, security-focused, high performance operating system. In this video, Qualcomm breaks down how upstreaming, open standards, and Canonical solutions help developers move faster, from first boot to production.
How Cisco Revolutionized Platform Engineering with Komodor's Agentic AI
In the world of cloud-native infrastructure, complexity is the silent killer of innovation. For Cisco Outshift, the company’s incubation engine, managing a sprawling environment of AWS EKS clusters and edge-based MicroK8s workloads created a classic bottleneck: the Platform Engineering team was drowning in toil. Facing SRE burnout and the limits of human scaling, Cisco embarked on an ambitious journey to evolve its internal operations from standard DevOps to Agentic AI.
[Open beta] Introducing Tests in Bitbucket Pipelines
If you’ve ever watched a pull request sit for hours because of a flaky test, you know how quickly test suites can turn from safety net into bottleneck. As teams grow, test suites tend to grow even faster because every new feature, bug fix, and regression adds more tests, while old or redundant tests are rarely cleaned up, so over time you end up running far more tests than are strictly needed for reliable feedback.