ankra project
Manage the organisation’s projects. A project is a scope inside an organisation. Clusters, applications, environments, stack profiles, pipeline repositories and AI automations each belong to exactly one project; credentials, registries, backup vaults, buckets, organisation variables, notification routes and DNS zones belong to one project or are organisation-wide (visible in every project). Members, roles, billing and settings stay organisation-wide. Every organisation has a default project, and until an administrator creates another one nothing changes. Which project a command acts in: the global--project <id|slug> flag (or
ANKRA_PROJECT) for one invocation, else the selection ‘ankra project switch’
saves on this machine, else the current project the platform remembers for
you (the one the portal shows). ‘ankra project current’ says which applies.
Not to be confused with ‘ankra registry projects’, which are the projects of
the organisation’s container registry (a Harbor concept).
Projects are turned on per organisation. While they are off, every project
command exits 3 saying so.
ankra project create
Create a project. The slug is derived from the name unless--slug names one:
lowercase letters, digits and hyphens, at most 63 characters. It never
changes afterwards - it ends up in kubeconfig entries, CLI selections and
deep links - so pick it deliberately.
ankra project current
Show the project this CLI acts in, and why (flag, saved selection or the platform’s current project)ankra project delete
Delete a project. The default project cannot be deleted, and a project that still holds resources is refused: move them with ‘ankra project move’ (or make the shared ones organisation-wide) first. Members whose current project it was are pointed back at the default project; tokens pinned to it stop working.ankra project get
Show one project by slug, name or idankra project list
List the organisation’s projects, the current one markedankra project members
List who reaches a project, and how (organisation role or project-scoped assignment)ankra project move
Move one resource to another project of the organisation (needs projects.manage).--kind names what moves: cluster, application, environment, stack_profile, pipeline_repository, ai_automation, ai_workspace
(each belongs to exactly one project), or credential, registry, backup_vault, object_storage_bucket, organisation_variable, notification_route, dns_zone
(which may also be organisation-wide). --id is the resource’s id; for a
cluster or an application its name works too. --to is the destination
project by slug, name or id, or ‘org-wide’ to make a shared resource
visible in every project.
A cluster carries its DNS zones, incidents and tickets along; an application
carries its connected repositories; a stack profile carries its drafts. A
cluster with operations still running is refused until they finish, and a DNS
zone bound to a cluster follows that cluster instead of moving on its own.
Role assignments scoped to a project keep their project: a cluster that
leaves it is no longer reached by them.
ankra project rename
Rename a project. The slug never changes; pass--description to change the
description in the same call.
ankra project switch
Switch to another project of the organisation. The platform’s current project moves with you (the portal follows), and the choice is saved on this machine beside the organisation selection, so later commands act in it until you switch again or run ‘ankra org switch’. A token pinned to a project cannot switch; pass--project for a single command instead.