Kubernetes 1.22 brings 56 enhancement, including a replacement for PSP, a rootless mode, and suport for Cgroupsv2. Discover more!

Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations. - n8n-io/n8n

n8n is a free and source-available workflow automation tool

Ortelius is a microservice catalog that centralizes supply chain and DevOps Intelligence into one location. Use Ortelius to expose microservice version drift across clusters, aggregate SBOMs to &am...

Welcome to the Ortelius Open Source Project Site

A Kubernetes operator for declarative database schema management (gitops for database schemas) - schemahero/schemahero

In Cloudflare’s core data centers, we are using Kubernetes to run many of the diverse services that help us control Cloudflare’s edge. We are automating some aspects of node remediation to keep the Kubernetes clusters healthy.

by Rich Burroughs

“No, we don’t use Kubernetes”. That always gets raised eyebrows... so we decided to write about our reasoning behind this cloud architecture decision.

If you've been part of an On-Call rotation, you know how a bad setup will leave you (literally) sleepless. Let's work on fixing that

Explore this post and more from the RedditEng community

4 best practices for breaking down silos and establishing a culture of shared responsibility toward reliability.

Our recommendations for configuring basic Kubernetes mechanisms to run your apps smoothly. That includes update strategies, priority classes, requests & limits, probes, and more.

Kubernetes is a big and complicated technology and it clearly requires some time and dedication to wrap your head around. There is no vendor lock-in meaning it runs the same no matter which managed cloud platform you use it on. This means using it lo...

This article summarizes how we see the "cloud computing and DevOps" space in 2021, which focuses on fundamental infrastructure and operational patterns, the realization of patterns in technology frameworks, and the design processes and skills that a software…

Just how many weird Resource Records can you stuff into a zone file? And what do these weird RRs actually return?

Or how programmers and testers can work together for a happy and fulfilling life. Why don’t we just automate all the testing? Is test coverage a useful metric? What does it mean to “shift testing left”? When and where should we be testing? How much is enough…