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.

Consider the scenario where a complex product is being developed by dozens of engineers working on different features of a product. Not only the development environment is the same, but the staging environment is also shared. As different features are merged into the shared environment, they break the code. So QA has to wait until this is fixed. A feature or bug fix may be working perfectly on the developer’s own machine, but there is no way for the QA team to test that one feature in isolation.

At CloudZero, we’re confident that we can organize cloud spend better than anyone else out there. For years, we’ve helped companies to efficiently organize spend, while overcoming traditional hurdles to visibility, like shared cost, incomplete tagging, and Kubernetes. We’ve helped customers who have struggled to attribute spend to do so in a matter of days — without saddling engineering teams with new projects or embarking on a resource tagging expedition with no end in sight.

Let's face it: no one likes patching. When I was a practitioner, we always put off patching until it was absolutely necessary. Until a business need – such as updating an application version or support ending for a version – arose, we didn't patch because "If it ain't broke, don't fix it." We all know this is a bad practice; let's remind ourselves why. The longer a system goes without being patched, the more changes will accumulate.

Sysadmins, short for system administrators, serve as a crucial subset of IT engineers and support staff and are often under-appreciated. Sysadmins are the lynchpins that provide continuity, performance, and security to the systems that connect every corner of the world. When COVID-19 scattered large workforces in offices across small home office networks, organizations relied on their sysadmins more than ever before to maintain work processes.

Today we are pleased to announce GitLab support on CircleCI. Teams using GitLab SaaS can now build, test, and deploy on CircleCI, and access CircleCI’s most popular features like Docker layer caching and automatic test-splitting. GitLab is now the third version control system we support, in addition to GitHub and Bitbucket.

Spot by NetApp is excited to announce that Spot Security is now generally available. Delivering continuous, automated security, Spot Security analyzes, detects, and prioritizes threats to surface the most critical risks and anomalies, while providing prioritized recommendations, guided remediation, and compliance.

GitHub is one of the most popular source control platforms available. It relies on Git concepts, and millions of developers use it. GitHub Actions embrace all aspects of what source control needs, such as branching, pull requests, feature flags, and versioning. It also integrates nicely into third-party continuous integration and continuous development (CI/CD) pipelines or deployment tools like Azure DevOps, Jenkins, GitLab, and Octopus Deploy.