A Project is Kargo’s organizational unit for a team or service. Creating one provisions a Kubernetes namespace with the same name and configures the RBAC its controllers need. Warehouses, Stages, Freight, and Promotions for that Project live in its namespace. section 3.2.5
Projects form Kargo’s isolation boundary: separate teams can use separate Projects, namespaces, Warehouses, Stages, and RBAC. A minimal Project needs only a name; promotion policies and project-level RBAC are optional. section 3.2.5
Create and verify a Project
Apply the Project manifest, then check that both the Project resource and matching namespace exist. If the namespace is NotFound, check the Kargo controller logs. section 3.5.2
Figure 3.1 Kargo’s core resource model. A Project defines the team-or-service scope (a Kubernetes namespace plus its RBAC). Inside that scope, a Warehouse discovers artifacts and produces Freight. A Stage is a node in the promotion graph; it subscribes to Freight, owns a promotion policy, and owns the Promotion objects that record each advancement event. Every Promotion ties a specific Freight to a specific Stage, recording who advanced it and with what outcome.
Trace how a Project scopes the resources involved in an artifact’s path through discovery and promotion. section 3.2
