About projects
How projects isolate your instances, clusters, storage, and networks, and what the project Summary page shows.
A project is the isolation unit in Akasha. Everything you create — instances, Kubernetes clusters, storage volumes, buckets, networks, profiles, and images — lives inside a project, and users are granted access per project.
The project selector
The project selector sits at the top of the console sidebar. It lists the projects you have access to, with each entry showing the project name, description, and instance count; a search box appears when you have many projects. Selecting a project opens its Summary page.
The selector also offers an All projects view. It shows instances from every project you can access in a single list; the other sections (Kubernetes, Networking, Storage, Images) require you to select a specific project first.
What lives in a project
- Instances (containers and virtual machines) — see About instances
- Managed Kubernetes clusters — see About Kubernetes on Akasha
- Storage volumes, buckets, and custom ISOs — see About storage
- Networks, ACLs, and forwards — see About networking
- Profiles — see Profiles
- Images — see About images
Feature isolation
Each project can keep its own isolated set of images, profiles, networks, storage volumes, and buckets, or share some of these with the platform's default project. Which features are isolated is decided when an administrator creates the project. For example, in a project without isolated profiles, the profiles you see come from the default project.
Feature isolation can only be changed while a project is empty, so treat it as fixed once you start creating resources. See Manage projects for details.
Resource limits
Administrators can set limits on a project: the maximum number of instances, containers, virtual machines, and networks, and the maximum total CPU, memory, disk, and processes across all instances. Limits are enforced when you create or resize resources — if a request would exceed a limit, it is rejected.
The Summary page
Each project's Summary page is its landing page. It shows:
- Overview cards: instances (running and total), containers, virtual machines, profiles, networks, storage volumes, images, and Kubernetes clusters.
- Resource usage bars: CPU cores and memory allocated against the project limits, live memory in use, and storage used against the disk limit (or "no project limit" when unset).
- A storage breakdown and, when clusters exist, a Kubernetes section with cluster and worker-node counts.
- The project's configured limits.
The Summary page also has a Billing tab that shows metered usage for the project — see Usage and billing.