IP alias for database

[r3ps4J]

Is there an existing feature request for this?

• I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

Right now you can define an IP alias for allocations on nodes, but not for databases. I'd like to request having it there too. Why is this useful? Let me explain.

A database is often located on the same server as the panel or wings, and from there you would use 127.0.0.1 to connect to it or perhaps use "database" if you're database container is called that in a docker compose set up. This results in 127.0.0.1 being shown to users as the endpoint. Obviously they can't connect with that, as it's only reachable on the local network with that ip.

The ideal ip to use for a database on the same network as wings would be to use host.docker.internal. This resolves to the host ip and let's you access services on the host as described here: https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host. Since wings spins up docker containers, this would be great to use for the configuration in a server. However, this will not allow the panel to connect to it, so this would be an additional field. Is this something that is achievable?

Describe the solution you'd like.

Ideally, to split up the database connection field in three fields.

• How the panel should connect to it (say a local ip like 10.0.0.42 if your panel is hosted on a different server on the same network).
• How servers can connect to it (host.docker.internal when you have a database on the same server as a wings node). It might be too big of a request, but perhaps even specifying it per node, or limiting access to the database per node. Since you could use a database from one node on another node, but I would say you could also add a note beneath the field to let people use common sense and not try to connect to the database from another node when using host.docker.internal.
• How users should connect to the database (usually a fqdn pointing to the node and port)

Additional context to this request.

I've set up a database on each node to reduce the round trip time from a server to their database.

Found this related issue, but it's not exactly the same and was fixed by just allowing a fqdn in the host field: #982

If you have any questions, ask away!