If you have a multi-cluster EKS deployment for your development, QA and staging environments, those generally don't need to run at 3AM. No one is using any of that, except for maybe a few cronjobs to refresh data. Everything else is wasted idle compute.

A developer writes a Dockerfile, adds a secret to set something up, then deletes the file a few lines later and pushes the image. From the container's perspective, the file is gone. But the secret is still in the image — permanently — and anyone with access to the image can pull it out with nothing more than tar and a few shell commands.

Here's the thing: cert-manager can issue that cert too. It can issue certs for anything you own a DNS name for, whether it runs in Kubernetes or not. Most teams don't know this.

Extracts CRD schemas from Kubernetes or YAML, converts Kubernetes built-in resource schemas from /openapi/v2, and publishes a searchable documentation site with interactive schema pages.

How we built an in-process client-side load balancer for a million requests per second of internal fan-out traffic, what we layered on top (N-ring fade-in, occupancy-based bounded load, and AZ-aware routing with a latency health factor), and how hardening that path cut cost and made the service resilient to the infrastructure underneath it.

Our insurance platform was tested with 50 insured objects maximum and that also took around 10 minutes for the end to end policy creation. And this happened via an asynchronous batch job which started after the user uploaded a csv file with the input data. And our goal was to do it for 100k insured objects in 20 minutes max.

A practical way to give every feature branch its own production-like environment without multiplying infrastructure complexity.