Skip to main content
POST
Bind an explicit application namespace

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
application_id
string<uuid>
required
cluster_id
string<uuid>
required
namespace
string
required
Required string length: 1 - 63
Pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
allow_planned
boolean
required
local_only
boolean
required
expected_revision
integer<int64>
required
Required range: x >= 0

Response

Success

id
string<uuid>
required
application_id
string<uuid>
required
organisation_id
string<uuid>
required
cluster_id
string<uuid>
required
namespace
string
required
region
string
required

Physical cloud region of the placement, for example eu-north-1. It locates infrastructure; it is not the data-location promise, which is data_boundary.

Required string length: 1 - 63
Pattern: ^[a-z][a-z0-9]*(-[a-z0-9]+)*$
data_boundary
string
required

Boundary the data is permitted to stay within, for example eu. Sharing a service across clusters is decided by this boundary, never by the physical region.

Required string length: 1 - 63
Pattern: ^[a-z][a-z0-9]*(-[a-z0-9]+)*$
policy_revision
integer<int64>
required
Required range: x >= 1
binding_revision
integer<int64>
required
Required range: x >= 1
binding_kind
enum<string>
required
Available options:
planned,
installation
installation_id
string<uuid> | null
required

The application installation the binding resolves to; null for a planned binding (binding_kind planned), which has no deployment yet. An installation identity does not imply readiness.

local_only
boolean
required