An admission controller for your own infrastructure

Forty engineers create containers, and the naming convention survives about a week. Untagged machines pile up; nobody knows which team owns box lucky-panda-7.

The Hoody API is HTTP, so you put a hoody-exec script in front of it. The team's tooling points at the interceptor instead of the API. Creation requests get inspected: no team tag, no cost-center label, wrong naming pattern: rejected with a message saying exactly what to fix. Compliant requests forward through untouched.

On other platforms this takes an admission webhook and a control plane willing to call it. Here it's a file, because the control plane is just another URL.

The naming convention stopped being a convention.