Manage CNAME/A/TXT records under the organisation’s own delegated DNS
zone (shown by ‘ankra org dns zone’). Records are reconciled asynchronously:
a new or edited record starts in state pending and turns active once it is
published to the authoritative nameservers.ankra org dns zone
ankra org dns list
ankra org dns add chat CNAME lb-1234.example-lb.com —ttl 300
ankra org dns update chat target.example.com
ankra org dns delete chatCreating, editing, and deleting records requires organisation admin.
Add a record to the organisation’s delegated zone. The name is the label
inside the zone (the zone fqdn is appended server-side), the type is one of
CNAME, A, or TXT, and the content is the record target.ankra org dns add chat CNAME lb-1234.example-lb.com —ttl 300
ankra org dns add app A 203.0.113.10
ankra org dns add eu TXT “v=spf1 ~all”
Re-point a record at new content. The record is referenced by its id or
by its name (the label or the full fqdn); the name and type of a record
never change - delete and re-add to rename. Pass —ttl to change the ttl at
the same time.
ankra org dns update <record> <content> [flags]
Flags
Flag
Default
Description
--ttl
0
TTL in seconds (30..86400); omitted keeps the record’s current ttl
--type
Record type (CNAME, A, TXT) to disambiguate a name reference
Invite a user by email to the current organisation.Valid roles: owner, admin, operator, member (default), viewer, read-only.
owner/operator alias onto admin/member on the invite until the RBAC
assignments API ships; run ‘ankra org roles’ for the full list.Examples:
ankra org invite user@example.com
ankra org invite user@example.com —role admin
ankra org invite user@example.com —role viewer
ankra org invite <email> [flags]
Flags
Flag
Default
Description
--role
member
Role for the invited user (owner, admin, operator, member, viewer, read-only)
Manage organisation-scoped variables that are available to every cluster
in the organisation as template substitutions in stack manifests and addon
values.ankra org variables list
ankra org variables get DB_HOST
ankra org variables set DB_HOST db.prod.example.com —description “Primary database”
ankra org variables delete DB_HOSTVariable resolution order at deploy time is stack > cluster > organisation; a
more specific scope overrides a less specific one.
Create or update an organisation variable (upsert). If the variable
does not exist it is created; otherwise its value (and description, when
supplied) is updated.The value can also be read from stdin by passing ”-”:echo “secret-token” | ankra org variables set API_TOKEN -