3 ms·

Did davestephen's comment help though? Apart from suggesting a .local domain... that's a bad idea, try .lan instead. Then you could type (for Plex, for example

• tachion 6y ago
  I know how to solve this problem, so I wasn't commenting on his comment, but rather on the fact that none of these tutorials so far solve this problem for new users that they target. Aside from that, I don't think what he proposes is a great solution, because what we'd need is the automated way for deployments to get that DNS created (or announced) for their IP when they get it or when it changes. Having it done manually and being static is vastly different in usability from k8s does with ingress/cloud controllers.
• 411111111111111 6y ago
  Dns is part of stock k8s. It usually runs on the 10th ip of the services network. It's the first service that goes up after you've initialized the cluster and initially serves only internal requests. Nothing stops you from pointing the matching lookup zone to the internal dns of k8s, however. I've done it before and it worked great for lan requests. If you want to expose it to the internet however, an automatically configured dns is probably not what you want, unless you actually have a public ip range to use with said services. In that case, the original comment makes more sense and you'd just add a wildcard dns to your ingress controller, which can be traefic or whatever else you want