> My personal opinion is that they do too much; if you name your syslog port "grpc" by accident, goodbye traffic! What was supposed to be documentation is now j

> My personal opinion is that they do too much; if you name your syslog port "grpc" by accident, goodbye traffic! What was supposed to be documentation is now just an undocumented part of the Kubernetes API. To be fair, a LOT of things in the Kubernetes world can rely on port names. Service and Ingress resources can use them to target ports on pods (or services, in the case of Ingress resources). Port names are responsible for the name of DNS SRV protocol specifiers for headless services as well.