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
  • Cluster
  • Project
  • Namespace
  • Services with a custom resource model
  • Access management
  • Quotas
  1. Concepts
  2. Resource model

Resource model

Written by
Yandex Cloud
Updated at April 8, 2026
  • Resource hierarchy
    • Cluster
    • Project
    • Namespace
  • Services with a custom resource model
  • Access management
  • Quotas

Stackland uses a hierarchical resource model allowing you to group the resources, perform access management, and apply consumption quotas at different levels.

Resource hierarchyResource hierarchy

ClusterCluster

A cluster is a root Stackland entity. At the cluster level, you can manage the following:

  • Cluster nodes.
  • Platform configuration (PlatformConfig).
  • Components (ComponentInstallation).
  • Cluster roles and role bindings (ClusterRole, ClusterRoleBinding).
  • Federations with external IdPs.

ProjectProject

A project is a logical grouping of namespaces for a team or application. At the project level, you can manage the following:

  • Project namespaces.
  • Project roles and role bindings (ProjectRole, ProjectRoleBinding).
  • Project resource quotas.
  • IAM access bindings (ProjectAccessBinding).

For more information, see Projects.

NamespaceNamespace

A namespace is a standard resource isolation unit in Kubernetes. A namespace contains the following:

  • Workloads (Pod, Deployment, StatefulSet).
  • Services (Service, Ingress).
  • Resources of the platform services (PostgreSQL and Apache Kafka® clusters, Object Storage buckets).
  • Roles and role bindings (Role, RoleBinding).
  • Access bindings (AccessBinding).

Services with a custom resource modelServices with a custom resource model

Some services have a resource model of their own, different from the Stackland hierarchy. Such services are deployed as stand-alone installations with their own UI. Within these services, access management uses their native mechanisms.

Access managementAccess management

You can grant access at any hierarchy level:

  • At the cluster level, via ClusterRoleBinding or ClusterAccessBinding. For access to all the cluster's resources.
  • At the project level, via ProjectRoleBinding or ProjectAccessBinding. For access to all the project's namespaces.
  • At the namespace level, via RoleBinding or AccessBinding. For access limited to a particular namespace.

To learn more, see Access management.

QuotasQuotas

You can set quotas at these two levels:

  • At the project level to limit the total of resources consumed by all the project's namespaces. This quota is set by the cluster administrator.
  • At the namespace level via Kubernetes' standard ResourceQuota mechanism. This quota is set by the project administrator.

For more information, see Setting project quotas.

Was the article helpful?

Previous
Projects
Next
Overview
© 2026 Direct Cursus Technology L.L.C.