Allow overriding managed FQDN with a custom domain #581
No reviewers
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!581
Loading…
Reference in a new issue
No description provided.
Delete branch "custom-fqdn-override"
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?
Add an "Advanced" escape hatch on the FQDN field: when a service offering restricts the FQDN to a managed wildcard subdomain, any user can now open a modal to set a fully custom domain instead. The modal explains DNS/TLS responsibility and shows the CNAME target to point at.
The override is inline (single custom domain, suffix addon removed, DNS warning shown, with a reset-to-managed link) and is detected on the edit form so saved custom domains round-trip correctly. Validation is client-side only; the CRD form already accepts arbitrary FQDN values.
Add an instance-aware ServiceInstance.ingress_cname so the detail page surfaces the CNAME exactly when an instance uses a custom domain. Also fixes two latent fqdn.js bugs (suffix force-appended on submit, DNS warning gated on !restrict).
514c4a13e5baef1db54ebaef1db54ec54146c7cfc54146c7cf9861997d78