Configure frontend custom domain
Changed onConfigures one custom domain for a frontend. The default Volcano-generated frontend URL remains active. Wildcard Volcano frontend TLS remains valid and isolated from custom-domain certificate changes. The account must own the hostname: it must have verified the hostname or a domain above it (see POST /user/domains). A certificate does not prove ownership. When the account owns no domain covering the hostname, Volcano asks for a TXT record at _volcano.<registrable domain>, such as _volcano.example.com. Publishing it verifies the whole domain, so later subdomains need no record. A managed TLS request reserves the hostname and returns that record in verification_records; the reservation expires after 72 hours unless the record is published. A BYOC request gets 409 with code: ownership_verification_required and the record in required_record; publish it and send the same request again. Managed TLS then returns the CNAME that authorizes certificate issuance and renewal. An unverified reservation does not block an account that proves ownership. When another account holds one, a request gets 409 with code: ownership_verification_required and the caller's own required_record; after publishing it, the same request takes over the reservation. When another account verified the domain, the same 409 names the record that moves the domain to the caller once the other account's record is no longer published. A hostname below a domain another account owns otherwise returns 409 without code.
Request
- Base URL: https://api.volcano.dev
- URL: https://api.volcano.dev/projects/{id}/frontends/{frontendId}/domain
- Auth: one of:
- HTTP bearer
- HTTP bearer
Path parameters
Project ID
Frontend ID
Request body
Response
Custom domain already configured with same hostname
Changes
- ○
the endpoint scheme security
ProjectAccessTokenwas added to the API
- ○
- ▲
the response's body type changed from
objectto no type for status - ▲
the
response's property type changed fromobjectto no type for status - ▲
the
response's property type changed fromobjectto no type for status - ▲
removed the required property
from the response with the status - ▲
removed the required property
/from the response with the status - ▲
removed the required property
/from the response with the status - ▲
removed the required property
/from the response with the status - ▲
removed the required property
/from the response with the status - ▲
removed the required property
/from the response with the status - ▲
removed the required property
/from the response with the status - ●
the
request property's maxLength was set to253 - ●
the
/request property's maxLength was set to65536 - ●
the
/request property's maxLength was set to65536 - ●
the
/request property's maxLength was set to65536 - ●
removed the optional property
from the response with the status - ●
added the new
failedenum value to theresponse property for the response status - ●
added the new
failedenum value to theresponse property for the response status - ○
the request property
/became optional - ○
the request property
/became optional - ○
added the new
managedenum value to the request property/ - ○
added
subschema #2to the response bodyallOflist for the response status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added to the
response propertyallOflist for the response status - ○
added to the
response propertyallOflist for the response status - ○
response property
required_routing_recorddeprecated - ○
response property
required_routing_recorddeprecated
- ▲