Generate FQDN from Wildcard Ingress per Control-Plane #203
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: servala/servala-portal#203
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 formapps.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.fqdnand 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.comThis has to happen dynamically on the frontend, because the user can type any name in the Name field.
Generat FQDN from Wildcard Ingressto Generate FQDN from Wildcard Ingress per Control-PlaneWorks like a charm