Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Stackland
  • What's new
  • Installation
    • All tutorials
    • Installing Stackland on Yandex BareMetal
    • Setting up external access to a pod in a cluster
    • All guides
    • Projects
    • Resource model
  • Access management
  • Pricing policy
  • Diagnostics and troubleshooting

In this article:

  • Resource hierarchy
  • Main features
  • Namespace grouping
  • Access management
  • Quotas
  • Project structure
  • System projects
  • stackland project
  • default project
  • What's next
  1. Concepts
  2. Projects

Projects

Written by
Yandex Cloud
Updated at April 8, 2026
  • Resource hierarchy
  • Main features
    • Namespace grouping
    • Access management
    • Quotas
  • Project structure
  • System projects
    • stackland project
    • default project
  • What's next

A project is a logical resource organization unit in Stackland. A project groups together several Kubernetes namespaces for access and quota management at the team or application level.

Resource hierarchyResource hierarchy

Stackland uses a three-tier hierarchy:

  • Cluster: Top-level entity that includes all Stackland resources.
  • Project: Logical grouping of namespaces for a team or application.
  • Namespace: Standard Kubernetes namespace used to isolate resources.

Each namespace belongs to a single project.

Main featuresMain features

Namespace groupingNamespace grouping

A project groups together several namespaces you want to manage in the same way. This helps with:

  • Organizing development environments (dev, staging, and production).
  • Separating microservices within an application.
  • Managing team or department resources.

The names of project namespaces must be prefixed with <project_name>-. For example, for a project named billing, namespaces can be named billing-backend or billing-frontend.

Access managementAccess management

At the project level, you can assign roles to users and groups:

  • Project-level roles automatically apply to all namespaces within the project.
  • Project administrators can independently manage access without involving the cluster administrator.

For more information, see Configuring roles in a project.

QuotasQuotas

A project allows you to set shared resource quotas:

  • Limits on total CPU and memory usage across all project namespaces.
  • Limits on storage capacity.
  • Limits on the number of GPUs.

A cluster administrator sets quotas when creating or updating a project. If total resource usage across all project namespaces exceeds the set quota, you will not be able to create new resources.

For more information, see Setting project quotas.

Project structureProject structure

When you create projects, Stackland automatically creates system namespaces in the project-<project_name> format. These namespaces contain project management resources, such as ProjectNamespace, ProjectRole, and ProjectRoleBinding.

System namespaces are not used for user workloads.

System projectsSystem projects

stackland projectstackland project

When deploying Stackland, the system automatically creates a project named stackland. This project includes all system namespaces, such as stackland-console and stackland-monitoring.

default projectdefault project

When deploying Stackland, the system automatically creates a project named default. Namespaces created without an explicitly specified project are automatically added to the default project.

Namespaces in the default project may have no default- prefix. However, their names cannot start with stackland- or project-.

You cannot delete the default project.

What's nextWhat's next

  • Creating a project
  • Managing namespaces in a project
  • Configuring roles in a project
  • Setting project quotas

Was the article helpful?

Previous
Upgrading a cluster
Next
Resource model
© 2026 Direct Cursus Technology L.L.C.