Operations | Monitoring | ITSM | DevOps | Cloud

Ah, the romance of the railroad. Conductors shouting “all aboard”, watching the countryside whizz by, dining cars and sleeper cars, boxcars, the Orient Express, bullet trains, chasm-spanning bridges, the clickety clack of the rails, clang clang at the crossings, and the engineer waving from the caboose. As we near the two hundred year mark of the first passenger train in 1825, we can observe that railways, our oldest modern means of mass transportation, are as strong as ever.

I am excited to share that we’ve just launched our first open source project called ValidKube. The idea behind Validkube is to fuse together the capabilities of three other popular open-source projects (kubeval, kubectl-neat and trivy by Aqua) and present them in a single view, providing users with a way to ensure YAML code hygiene and security, all at the same time and with just a few clicks of the button.

What makes an engineering team? Communication, collaboration, process, order, and common goals. Otherwise, they would just be a bunch of engineers. The same is true of their tools. Connectivity and process turn a bunch of tools into a DevOps toolchain. If you need a DevOp toolchain, you can use it to easily build an incident response process.

The number of internet-connected assets around us that are powering services and utilities in a wide array of sectors is rising at an exponential rate. As a result, it’s becoming critical for businesses that provide such services and utilities to have an observability stack tailored to the type of physical hardware devices that are generally deployed in swarms.