Operations | Monitoring | ITSM | DevOps | Cloud

Small confession: we currently use the term 'post-mortem' in incident.io despite preferring the term 'incident debrief'. Unless you have particularly serious incidents, the link to death here really isn’t helping anyone. However, we're optimising for familiarity, so we're sticking to the term 'post-mortem' here. Ask any engineer and they’ll tell you that a post-mortem is a positive thing (despite the scary name).

As more companies adopt SaaS services over on-premise delivery models, there is a natural concern around data security and platform availability. Words on a vendor’s website can provide insights to prospective customers on the process and policies that companies have in place to alleviate these concerns. However, the old adage of “actions speak louder than words” does apply. Trust in a website’s words only goes so far.

Waste is never a good thing. And rumblings of an economic downturn, alongside dire warnings of climate change, are making it increasingly necessary to address waste. As a society, we need to reduce consumption, data included. First, we all must acknowledge the high cost of data. Despite the prevailing opinion of the 2010s, data isn’t free. There’s a monetary and carbon cost to keeping data alive.

“Lead time to deploy” means the interval from when the code gets written to when it’s been deployed to production. It has also been described as “how long it takes you to run CI/CD.” How important is it? It’s nigh-on impossible to have a high-performing team if you have a long lead time, and shortening your lead time makes your team perform better, both directly and indirectly.

We are happy to announce the first minor release of Kubewarden v1.0: v1.1.1 is now available! For those of you new to Kubewarden, it is a policy manager for Kubernetes.

When considering application source code, the way you maintain consistency throughout environments is mostly straightforward. You write application code, commit it to source control, and then build, test and deploy via a CI/CD pipeline. Since the application is defined by the source code living in source control, the build will be identical in all environments to which it’s deployed. But what about the infrastructure on which an application runs?

We have covered a plethora of topics on Active Directory (AD) in parts one to nine of this series on Active Directory Domain Services. In this final and 10th part, we will look at one other crucial aspect of AD—Group Policies and Group Policy Objects (GPOs). We will discuss what Group Policies are and what role GPOs play in the effective setup of any AD environment.