Actions31
- Backup Actions
- Backup Share Actions
- Catalog Actions
- Cube Actions
- Domain Actions
- Snapshot Actions
- TCP Mapping Actions
- Webhook Actions
Domain → Create
AI-generatedSummary
Attach a custom domain to a Cube in a Space by sending a POST request to Krova Cloud. Set the domain, destination port, and origin scheme; optional PROXY protocol settings control connection headers sent to the Cube.
Inputs
- Space ID (required) — ID of the Space that owns the Cube.
- Cube ID (required) — ID of the Cube to attach the domain to.
- Domain (required) — Domain name to attach, such as app.example.com.
- Port (required) — In-Cube port that receives traffic; defaults to 8080 and must be from 1 to 65535.
- Origin Scheme — Transport used from the edge to the Cube: HTTP by default, or HTTPS if the Cube terminates TLS itself. Visitors use HTTPS either way.
- Additional Fields: PROXY Protocol — Choose Off (default), V1, or V2. When enabled, sends a PROXY protocol header with the visitor address. The app must accept that protocol on the selected port, and all domains on that Cube port need the same setting.
- Additional Fields: Confirm Mixed PROXY Protocol — Whether to proceed when other domains on the same Cube port use a different PROXY protocol setting. Without confirmation, such a save fails with HTTP 409.
Output shape
A single API response item for the created domain mapping.
The operation sends the required domain and port, plus the selected origin scheme. PROXY Protocol Off is sent as null to clear the setting; the mixed-setting confirmation is sent when configured. The source does not specify the response fields.