There are two hard problems in computer science: naming, cache invalidation, and off-by-one errors. In this lightning yet lighthearted talk, we'll show a few areas where Kubernetes chose rather confusing names, and we'll (try to) explain why. Exhibit A: services (we can't start/stop them in Kubernetes). Exhibit B: services strike back (you don't need a LoadBalancer service to do load balancing). Exhibit C: return of the services (ExternalNames are not necessarily external, in fact, quite the contrary!). Exhibit D: apiVersion is not (just) the version of the API. If you know Kubernetes, this talk will help you to understand (or memorize) better how it works. And if you don't (lucky you, and is there a bit of room available under that rock?) you'll probably still have a good laugh (hopefully not at the expenses of the other folks).