>it costs me nothing to change my vocabulary

It cost reddit a 3 hour outage.

>The nodeSelector and peerSelector for the route reflectors target the label `node-role.kubernetes.io/master`. In the 1.20 series, Kubernetes changed its terminology from “master” to “control-plane.” And in 1.24, they removed references to “master,” even from running clusters. This is the cause of our outage.

https://old.reddit.com/r/RedditEng/comments/11xx5o0/you_brok...

Master/slave is almost always misused anyway. Yes one database will do all the work(we will call that one master) and the other will sit around all day waiting to take over(we call that one the slave). me nodding. yep that is about how it worked. postgres is a little closer where the master process hangs around not doing much, only really there to receive new connections which it then gives to workers to process. And don't even get me started on how IDE drives misused the term, I don't mind the master/slave terminology but if used it should at least capture some of the dynamic of that relationship.

I never did understand what they felt was wrong about git master, there was no slave or even work involved. it was more like the master print of a video. you know the thing that "remasters" are made from.