From a Hacker News comment describing an incident that was fixed globally modifying /etc/hosts in Kubernetes, and the fun term “temporary kludge shim” came up. Other great terms and great war stories swapped in top-level comments. “Manager-deactivating jargon” is going promptly into my back pocket.

SOLAR_FIELDS 16 hours ago | parent | next [–]

This reminds me of the time that Google’s Paris data center flooded and caught on fire a few years ago. We weren’t actually hosting compute there, but we were hosting compute in AWS EU datacenter nearby and it just so happened that the dns resolver for our Google services elsewhere happened to be hosted in Paris (or more accurately it routed to Paris first because it was the closest). The temp fix was pretty fun, that was the day I found out that /etc/hosts of deployments can be globally modified in Kubernetes easily AND it was compelling enough to want to do that. Normally you would never want to have an /etc/hosts entry controlling routing in kube like this but this temporary kludge shim was the perfect level of abstraction for the problem at hand.
reply

 
    citizenpaul 16 hours ago | root | parent | next [–]

    > temporary kludge shim was the perfect level of abstraction for the problem at hand.
    Thats some nice manager deactivating jargon.