Operations | Monitoring | ITSM | DevOps | Cloud

With the latest releases of Kubewarden v1.1.0 and the verify-image-signatures policy, it’s now possible to use GithubActions or KeylessPrefix for verifying images. Read our previous blog post if you want to learn more about how to verify container images with Sigstore using Kubewarden.

Naming conventions for assets have a rich, engaging, and often hilarious history. While recently organizations have switched to standardized and more informative naming conventions based on location and function, earlier (and even now) IT departments have had a lot of fun naming assets for their data centers and servers. IT departments have often showcased their inner geek by using names of Star Wars or Star Trek characters for their assets.

An incident has been declared and your runbook has fired. Everyone is gathered in your Slack channel, the tickets are opened, and roles are assigned. Now what? This is when most teams manually update status pages and kickoff investigation streams using a patchwork of tribal knowledge and supporting playbook documents.

Today’s data centers generate a lot of data. Intelligent rack PDUs and other metered power infrastructure, environmental sensors, and the constant change in modern data centers all contribute towards a massive volume and variety of data. But data center professionals don’t have the time to collect all the data from its sources, analyze it, and derive insights from it that improve their data center operations.

This video blew us away. In 15 seconds, Frito-Lay illustrated the deliciousness of Tostitos® Salsa comes down to 3 simple, wholesome ingredients with transparent packaging that enhances the flavor experience. With ultimate visibility, you can see the quality right through the jar. Man, we couldn’t stop talking about the genius of it all. We boiled that 15 seconds down even further. “3 ingredients. Chop, chop. Yum, yum.” (By my count, that’s 8 seconds)

Modern enterprises understand the need to move away from developing monolithic applications to ones that make best use of the cloud to enable business acceleration at scale and speed. That means transforming development to more resilient cloud native architectures that can be readily deployed to cloud, multi-cloud, and hybrid environments. What does it mean to be cloud native?

ITOps and DevOps are technology management practices that have been around long enough that anyone in IT should have a good grasp of what they mean. Here’s our experts’ take on ITOps vs. DevOps.

In a DevOps environment, continuous testing is essential to success. By automating the testing process, you can release new, bug-free code faster, and more efficiently. In this software development tutorial, we will examine continuous testing, its benefits, and best practices.