> This one's a new one to me, and apparently relies on some special new widgets. ExternalName has been around since 2016. > Nobody uses NodePort to expose ext

> This one's a new one to me, and apparently relies on some special new widgets. ExternalName has been around since 2016. > Nobody uses NodePort to expose external services directly, and I think you know that. Sure they do. Anyone using a LoadBalancer does this implicitly. If you don’t want k8s to manage the allocated port or want to use something bespoke that k8s doesn’t offer out of the box then using a NodePort is perfectly fine. You can also create a custom resource type if you’ve got some bespoke setup that can be driven by an internal API. The happy path is using a cloud load balancer, because that’s what you’d use if you are using a cloud provider and you’re comfortable with k8s wiring it all up for you. Has your criticism of k8s evolved from “I’m unclear about services” to “well yes it supports everything I want out of the box but uhh nobody does it that way and therefore it can’t do it”?