Generate FQDN from Wildcard Ingress per Control-Plane #203

Closed
opened 2025-09-26 12:33:26 +00:00 by tobru · 1 comment
Owner

Stories

As a user, I want to have a pre-generated FQDN to get going fast

Implementation Notes

Some services require an FQDN to be configured. This can either be a custom one which the user controls themselv, or a system provided.

Every control-plane has a wildcard DNS configuration already, e.g. *.apps.exoscale-ch-gva-2-prod2.services.servala.com. Allow configuring this wildcard DNS per control-plane, in the form apps.exoscale-ch-gva-2-prod2.services.servala.com (without the star and dot).

Use this information to generate an FQDN for services that have a field spec.parameters.service.fqdn and put the generated value into the service configuration field. The user can still change that, but it makes it a lot easier to get started fast.

Generate the name this way: $instancename-$organization_namespace.$control_plane_wildcard.
Example: myforgejo-org-42.apps.exoscale-ch-gva-2-prod2.services.servala.com

This has to happen dynamically on the frontend, because the user can type any name in the Name field.

## Stories _As a user, I want to have a pre-generated FQDN to get going fast_ ## Implementation Notes Some services require an FQDN to be configured. This can either be a custom one which the user controls themselv, or a system provided. Every control-plane has a wildcard DNS configuration already, e.g. `*.apps.exoscale-ch-gva-2-prod2.services.servala.com`. Allow configuring this wildcard DNS per control-plane, in the form `apps.exoscale-ch-gva-2-prod2.services.servala.com` (without the star and dot). Use this information to generate an FQDN for services that have a field `spec.parameters.service.fqdn` and put the generated value into the service configuration field. The user can still change that, but it makes it a lot easier to get started fast. Generate the name this way: `$instancename-$organization_namespace.$control_plane_wildcard`. Example: `myforgejo-org-42.apps.exoscale-ch-gva-2-prod2.services.servala.com` This has to happen dynamically on the frontend, because the user can type any name in the Name field.
tobru added the
enhancement
label 2025-09-26 12:33:26 +00:00
tobru added this to the Development Planning project 2025-09-26 12:33:26 +00:00
tobru changed title from Generat FQDN from Wildcard Ingress to Generate FQDN from Wildcard Ingress per Control-Plane 2025-09-26 12:33:46 +00:00
rixx referenced this issue from a commit 2025-10-17 03:44:54 +00:00
Author
Owner

Works like a charm

Works like a charm
tobru closed this issue 2025-10-17 07:52:50 +00:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: servala/servala-portal#203
No description provided.