IT professionals talk about automation… sometimes ad nauseum. We generally understand its value, even if we’re tribally divided by the specifics of its application. For civilians, automation is a catch-all for using technology to wield skills and abilities outside their experience (like placing an order through a complex infrastructure) and access the world of vendors and goods they wouldn’t have time to connect with on their own.

Ansible has become one of the most popular tools used by operations teams to automate their IT tasks. It allows them to quickly, and at the largest enterprise scale, manage the configuration of their IT systems. This includes software and infrastructure on-premise and in the cloud. Its open-source roots has allowed it to grow a large global community with an equally expansive ecosystem of integrations.

The number of publicly available Helm charts is continuously growing and while this is great for the community, it can be challenging to navigate the vast sea of Helm charts and Helm chart repositories. Like a ship’s captain, you need more than just a list of where you can go, but the details to ensure those under your charge arrive certainly and safely. Not just what can be seen on the surface, but what lies underneath, and the hazards that await.

Our 2020 SRE Report is ready! We launched the SRE survey 2020 this January with the goal of understanding the current state of SRE. The survey covered a range of topics including: As we neared the end of the survey period, the SRE community was in the midst of a sudden change. SRE teams were forced to migrate to all-remote IT. We realized we would not be able to provide an accurate analysis without considering this shift in how SRE teams were operating in this new environment.

Kubeflow Pipelines are a great way to build portable, scalable machine learning workflows. It is one part of a larger Kubeflow ecosystem that aims to reduce the complexity and time involved with training and deploying machine learning models at scale. In this blog series, we demystify Kubeflow pipelines and showcase this method to produce reusable and reproducible data science.

If you’ve been following along, the last two articles explained the CI/CD (Continuous Integration/Continuous Delivery) processes. In this article, we look at how Uptrends fits into those processes. Uptrends can fit into your CI/CD process in several different ways. For example, you may want to use Uptrends for the testing and monitoring portions, include your monitor updates as part of your automation processes, or both.

One of the most important aspects of any Chaos Engineering program is knowing that every experiment is being run safely. And one of the simplest ways to ensure safe experiments is by having safeguards that prevent running chaos experiments on a system that is unhealthy or has an incident in progress. Today, Gremlin is excited to announce Status Checks, which run before you kick off a Chaos Engineering Scenario in order to verify your system is in a steady state.

Building a healthy productive engineering culture is hard and just deploying frequently with continuous deployment is not enough. I'm going to show you how you can use a carrot, not a stick, approach to take continuous deployment to the next level by celebrating team values with Sleuth.

Responsibilities are shifting between software developers and operators due to the increasing adoption of agile development practices, DevOps, and GitOps. This makes it challenging for developers and operators to effectively collaborate in order to increase developer agility and productivity. D2iQ’s Dispatch is built on a cloud native foundation, leveraging Tekton and Argo CD to simplify running CI/CD on Kubernetes with a simplified user experience.