[RFC] Using project and service specific DNS end points to support flexible deployments.

DJ Delorie dj@redhat.com
Fri Nov 6 18:06:15 GMT 2026


On Fri, Nov 6, 2026 at 11:10 AM Carlos O'Donell <carlos@redhat.com> wrote:
> Would you agree that doing {service, project} x DNS end points is orthogonal
> to the ingress scaling point you made?
>
> That is to say that we can always do ingress scaling.
>
> We should also do the DNS changes to allow moving services around easily.

All I mean is that if we do "project.host/service" we have one
ingress/dns path, and we can use internal reverse proxies to manage
service load and per-service dns without the users even knowing (aside
from removing an ingress point).

With service.project.host/ you need an ingress concentrator for each
service, and service dns changes are public-facing and thus affect
users and need to be scheduled much further in advance.  Plus you need
to manage far more public DNS entries - number of services times
number of ingress points.

The only real advantage of the per-service DNS style is services that
can't be https proxied, like smtp or git.

But I suppose a hybrid approach can be used -
https://project.host/service for anything that's an https url, and
service.project.host for anything that can't be reverse proxied.



More information about the Libc-alpha mailing list