CI/CD is a software development strategy which allows for faster development by introducing automation while still maintaining the quality of code deployed to production. Implementing a CI/CD pipeline not only promotes a safer deployment process but also improves the incident response process. CI/CD is broken down into multiple parts. The CI refers to continuous integration, meanwhile, the CD can refer to continuous delivery and/or continuous deployment.

We’ve had an exciting year here at Puppet, and although it’s not the year we could have expected, I’m encouraged and inspired every day by the resilience of our team, our commitment to each other, and our drive to help customers navigate through so much uncertainty and change.

Netdata is zero-configuration monitoring. It’s a principle that we’ve stood behind since the project’s beginning, when it was only our CEO Costa trying to solve a “painful, real-world problem,” and it’s one we stand by today. Our insistence on zero-configuration guides every product decision we make, every grooming process, and every React component our frontend teams design.

On our journey to democratize monitoring, we are proud to have open source at the core of both our products and our company values. What started as a project out of frustration for lack of existing alternatives (see anger-driven development), quickly became one of the most starred open-source projects on all of GitHub.

It's hard enough to run an operations center in the best of times, especially in large, complex environments supporting myriad applications. Some of the many challenges are: Now throw in the current set of challenges with personnel being remote, and the problems get compounded exponentially. The ability to "tap the shoulder" or "conference room huddle," while not always the most efficient to begin with, is no longer an option.

Modern applications are changing, and traditional testing practices are no longer up to the task. Learn more about the changing landscape of QA and how Chaos Engineering provides the necessary framework for testing modern applications. Chaos and Reliability Engineering techniques are quickly gaining traction as essential disciplines to building reliable applications. Many organizations have embraced Chaos Engineering over the last few years.

We created the Fleet Project to provide centralized GitOps-style management of a large number of Kubernetes clusters. A key design goal of Fleet is to be able to manage 1 million geographically distributed clusters. When we architected Fleet, we wanted to use a standard Kubernetes controller architecture. This meant in order to scale, we needed to prove we could scale Kubernetes much farther than we ever had.

By design and tradition, telecoms networks are built to last. But in a world where the rate of innovation seems to be accelerating, the end result is that a lot of legacy infrastructure needs to keep pace with, and accommodate, multiple ‘next generation’ phases. How long this can be maintained before the imperative to rip and replace becomes impossible to ignore is the multi-million-dollar question.

A few years ago, we realized that spending in our AWS product test environment had jumped significantly from one month to the next. We drilled down into the issue and traced it to some RDS database instances that had been spun up to test new product features. No one realized that these expensive instances were left running after the tests were complete, and subsequently racking up charges for several months.

Growth for an enterprise is an exciting thing, but it often presents a unique challenge for IT professionals. There are common roadblocks that are encountered when trying to upscale an IT management environment. In this first blog of our Managing IT Infrastructure at Scale series, we discuss the benefits of distributed monitoring data for large IT environments.