Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on DevOps, CI/CD, Automation and related technologies.

Announcing HAProxy Kubernetes Ingress Controller 1.5

We’ve released version 1.5 of the HAProxy Kubernetes Ingress Controller. This version unlocks access to the raw HAProxy configuration language for power users to gain more control. You can also enable mutual TLS authentication between the ingress controller and services, enforce Basic authentication, and return custom error pages to users.

Future of Monitoring: Experts Predictions for 2021 and Beyond

Making predictions is a tricky business at the best of times, but especially after a year that turned the world upside down. Even so, we have decided to talk to the IT leaders and discover what we should get ready for in 2021. With technology development, COVID-19 impact, and the new cybersecurity issues happening in the world, the IT engineers responsible for the IT infrastructure monitoring should be always ready to adapt to the new challenges.

Barriers to DevSecOps Adoption

DevSecOps — or the merging of Ops and Security — has been at the center of discussion for the better part of the outgoing decade. Today, the complexity of infrastructure change, demands security and DevOps teams to work together more efficiently. But there are hurdles to adoption of DevSecOps as a methodology. Cloud-native applications often live in multiple clouds across data centers, co-location, and public clouds.

Taming the compliance beast: achieve efficiency & reliability at scale

Regulatory compliance is time-consuming and expensive. A recent survey of IT security professionals found that, on average, organizations must comply with 13 different regulations and spend an average of $3.5M annually on compliance activities, with audit-related activities consuming 232 person hours per year. With a team of five people, that adds up to 1.5 months a year devoted to audit-related activity. That’s a lot of hours that could have been spent on initiatives driving customer value.

2021 is the Year of Reliability

There’s no better time than now to dedicate effort to reliable software. If it wasn’t apparent before, this past year has made it more evident than ever: People expect their software tools to work every time, all the time. The shift in the way end-users think about software was as inevitable as our daily applications entered our lives, almost like water and electricity entered our homes.

Trends in 2021 Dev-Led Landscape

Nowadays developers are in the driver’s seat regarding a lot of decisions for the tools they use. In this update from Tyler Jewell, he covers what he sees are the Top 5 trends that will take place this year. While it’s a bit of a crowded chart, he plots the companies that he sees driving these trends. If you drill into the Service Catalog trend, Jewell sees a couple of different groups working on ways to help developers deal with the deluge of Services (aka APIs).

How Service Providers Can Improve Network Performance in a Post-Pandemic World with Traffic Engineering

One thing that 2020 has clearly shown us is that communications services is a basic and fundamental driver of our global economy. During the COVID-19 pandemic, we realized that many tasks can be done at home, if access to communications services is sufficient. Many of us can work from home or other locations outside of the traditional office; students do not have to be physically present at school to participate in lectures; and we don’t need to go to movie theaters watch a new film release.

The Key Differences between SLI, SLO, and SLA in SRE

To incentivize reliability in your platform, there should be shared goals across your team to measure & quantify the capabilities of your product/service along with customer experience. Define the path of "Always-On" services by understanding few key SRE fundamentals and their implications - SLIs, SLOs & SLA. Framing SRE metrics for building or scaling a product is quite a daunting task.

Discord Bot Part 1: Getting started the right way

I’ve recently started working on a new project to build a Discord bot in Go, mostly as a way to learn more Go but also so I can use it to manage various things in Azure and potentially elsewhere. I figured it’d be useful to document some of this project to give some insights as to what I’ve done and why. First up was setting up the CI/CD pipeline for it so that I don’t need to worry about it later and can save myself a bunch of time when testing.